Hi Sukender,
I can't bu sure of how users could use it, but I think some users may find
purely rendering-oriented applications to such a code.
I think there would totally be rendering applications to a ProxyImage.
The most obvious one is that for applications like ours that open and
close windows / contexts, they currently have to disable the
unrefImageDataAfterApply setting, just in case another window could be
opened later. The disadvantage of this is that image data is then always
duplicated (in system memory and in graphics memory) just "in case"...
The image data takes up more memory 99% of the time so that the 1% or
even less of the time when a new window is opened, it will work.
If we had a ProxyImage as you suggest, then we could keep
unrefImageDataAfterApply turned on, and reclaim the CPU-side memory, and
then when a new window would be opened the images would be reloaded
transparently to be applied to the new context. Taking a bit more time
to open a new window (to reload the images) is not really a big issue in
this case.
So I think there's value in this beyond offline database processing. I
hope you can find a compromise that both Robert and you will be happy
with, so that this work can be integrated.
J-S
--
______________________________________________________
Jean-Sebastien Guay [email protected]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
