CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
m (→‎CompositeViewer: motivation comes first)
Line 198: Line 198:
{{WIP}}
{{WIP}}
-->
-->
The natural way to manage a application that was two views on to two different scenes is to use a osgViewer::View for each separate scene, and then a osgViewer::CompositeViewer to manage these two scenes.  These two views can share the same GraphicsWindow, or have their own.  They may even be added/removed from the CompositeViewer, or have their rendering toggled on/off via NodeMask's on the master Camera for each View.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg24466.html</ref>
The natural way to manage an application that has two views on to two different scenes is to use a osgViewer::View for each separate scene, and then an osgViewer::CompositeViewer to manage these two scenes.  These two views can share the same GraphicsWindow, or have their own.  They may even be added/removed from the CompositeViewer, or have their rendering toggled on/off via NodeMask's on the master Camera for each View.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg24466.html</ref>


The Viewer class is the simplist for of viewer and
The Viewer class is the simplist for of viewer and

Navigation menu