Hi Orhun, On 1/17/07, Orhun Birsoy <[EMAIL PROTECTED]> wrote:
I think GraphicsContext::Trait class will be much more appropriate for such requests. So I propose 3 types of window creation by setting Traits class variables. . new variable to Traits are (Window is a typedef for each platform window handle, something like Producer/Types) Window parent; Window window;
GraphicsContext::Traits is *no* place for Window specific handles. Its a window hinting structure for window creation. I am also against having typedef for each platforms window handle. Windowing specific code must all kept local to windowing specific implementation headers and not spilled out over the rest of the OSG. One of the key things about the new architecture is decoupling the various implementation from the underlying framework. If you have already created the window then you arn't asking osgViewer to create a window for you, you already have your windows, and you should find it easy to construct a platform specific GraphicsWindow and then do platform specific stuff like setWindow. You app could will platform specific anyway so there is real no loss in portability. So I'm open to seeing the platform specific implementations to allow construction with Triats and then using setWindow or similiar to provide an already created window. I'm not open to just adding windowing specific stuff to Traits, its not the place for this type of hardwiring. Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
