CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
Line 159: Line 159:
So we've always got the basic scenario to fall back on where there is just a single view and things are essentially identical to a standard non-CompositeViewer setup.<ref>https://sourceforge.net/p/flightgear/mailman/message/37076818/</ref>
So we've always got the basic scenario to fall back on where there is just a single view and things are essentially identical to a standard non-CompositeViewer setup.<ref>https://sourceforge.net/p/flightgear/mailman/message/37076818/</ref>


<!--
=== OSG stuff ===
=== OSG stuff ===
{{Note|As a general note, osgViewer::CompositeViewer should have osgViewer::View attached to it NOT osgViewer::Viewer. It's a composite of View's not composite of Viewer.  If you look at all the OSG example they illustrate the correct usage.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg70462.html</ref>}}
{{Note|As a general note, osgViewer::CompositeViewer should have osgViewer::View attached to it NOT osgViewer::Viewer. It's a composite of View's not composite of Viewer.  If you look at all the OSG example they illustrate the correct usage.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg70462.html</ref>}}
Line 224: Line 225:
onscreen one would give you means to visually QA things as you go
onscreen one would give you means to visually QA things as you go
along.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg70703.html</ref>
along.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg70703.html</ref>
-->


== Use Cases ==
== Use Cases ==

Navigation menu