Hi Robert, I've been investigating the reasons windows moved from one screen (i.e. display adapter) to another do not render properly (on the Win32 platform) and came to the conclusion that under Windows we basically need to rebuild the window completely from scratch when it is moved to a new display adapter (because we need to change its pixel format relative to the new target adapter and in Windows you cannot change the pixel format more than once).
My current idea for targeting this is to close and re-initialize the graphics context to have it setup properly for the new display adapter since such things as GL extensions, display lists, etc. need to be rebuilt as well. Looking at the code, I'm realizing that this may involve more work on the core OSG side, since not everything related to a given context ID seem to be cleaned up when it is freed (for example GL Extensions for the old context ID seem to be retained, display lists in drawables also, textures, etc.) This leads me to believe that the current code does not (for the moment) support the dynamic reuse of a previously access context ID; it will reallocate it but will not cleanup the previous information it held completely. Am I right on this or is there some code that will take care of disposing all such data when a contextID is freed ? André _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
