Hi Paul,

On 1/17/07, Paul Martz <[EMAIL PROTECTED]> wrote:
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.)

Horahh!!!!  ;-D

This is exactly how its supposed to behave, by default
osgViewer::Viewer calls View::setUpViewAcrossAllScreens if no windows
are already set up before you call viewer.realize().

Curiously osgProducer should also behave this way, so the fact that it
isn't suggest there is something amiss in Producer under Windows, as
under X11 Producer will automatically open up on all windows.
osgViewer::Viewer just follows this convention.


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.

Both of these will be separate EventHandlers.  Potentially we can
provide these off the shelf, but they won't be default parts of the
viewers like they were with osgProducer::Viewer.

With osgviewer my plan is to register a full range of event handlers,
both custom and off the shelf ones.   But for the rest of the examples
I'd like to keep there focused on the part of the OSG that they are
illustrating rather than building up everything and the kitchen sink
viewer like we had with osgProducer::Viewer.

The stats handling is an interesting challenge, update, event, cull
and draw stats will need collecting as well as displaying. The
collection of these stats will require changes to viewer classes as
well the core osg::GraphicsOperation class.  There is a huge amount of
scope for collecting stats - worthy of whole thread of discussion on
its right.  Perhaps a simple frame rate stats would be a way getting
at some stats feedback.

Robert.
_______________________________________________
osg-users mailing list
osg-users@openscenegraph.net
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to