No, this has nothing to do with decorations. My (dual-monitor) desktop is 2560x1024. In spite of that, osgProducer-based examples used to open a 1280x1024 window. However, osgViewer-based examples now open a 2560x1024 window. Apparently this was a bug in Producer's default Win32 RenderSurface (albeit one that I had grown accustomed to and expected). So, problem solved (apparently). Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com <http://www.skew-matrix.com/> 303 859 9466
_____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of André Garneau Sent: Wednesday, January 17, 2007 10:07 AM To: 'osg users' Subject: RE: [osg-users] GraphicsWindowWin32 window size issue Hi Paul, Are you requesting for window decorations in the traits ? The size specified in the traits are translated to be the size of the window client area, not the overall window size. So if your screen resolution is 1280x1024 for example and you request decorations (_traits->windowDecoration = true) and specify (0,0) as the window position with 1280,1024 as its width & height, then you will end up with the decorations overlapping on adjacent screens. The client area should start at the traits position and be of the requested size. If all you really want is a full-screen window, turn off window decorations and that should do the trick. Alternatively, if some people object that the position & size requested are applied to the client area instead of the whole window, this can be changed or better yet made configurable in the traits. Any opinion on this ? Agree on your side topic where statistics display is an important feature that should have high priority. Thanks for the feedback, André PIXDEV inc. [EMAIL PROTECTED] _____ De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Paul Martz Envoyé : January 17, 2007 11:37 AM À : 'osg users' Objet : [osg-users] GraphicsWindowWin32 window size issue I just checked out latest CVS and rebuilt to try out the new GraphicsWindowWin32 submission. One difference (compared to osgProducer) I noticed immediately is a difference in the window size. osgProducer-based examples open a fullscreen window on only one of my dual monitors; GraphicsWindowWin32-based examples open a window that spans both displays. I wanted to post this to make sure it was an intentional change to the default behavior. (FYI, I am using an NVIDIA GeForce graphics card running in dual-view mode.) On a slightly different topic, of the osgProducer-based example features that are not yet implemented, I'd rate the statistics display as the top priority, with the HUD help display as a close second. Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com <http://www.skew-matrix.com/> 303 859 9466
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
