Hi Jeremy,
viewer.setUpViewInSingleScreen(50, 50, w, h);
Yeah, that's no problem. :) I can add this easy.
OK good, that's at least a good start.
As for letting the viewer set itself up, there should be ways of getting
the size of the window after viewer.realize():
That's the key though--I wouldn't want to rely on the viewer being
realized, and it would make the code tricky to do properly in the right
order.
I don't think it's a problem. You have to pass the size anyways when
creating the WindowManager right? So you'll just defer creating your
WindowManager until the viewer is realized. Just calling
viewer.realize() yourself before viewer.run() does the trick...
Anyways, we're talking about examples here, where the polite thing is to
let osgViewer::Viewer set itself up however it likes. So if you need to
go through a few more hoops to do this, that's fine IMHO. In the case of
a real application, the user will probably know the size of their window
in advance, so the problem is non-existent.
The answer, I think, is me hacking osgViewer to report this data via the
RESIZE event properly, I'm just so overwhelmed with a sense of wanting
to "get this done" I haven't had a chance. :) It is something I will do
eventually, of course.
Perhaps hacking isn't the right word, I would say "fixing" instead :-)
(Wasn't trying to be inflammatory, if it sounded that way. :))
Nah, don't worry about it.
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
