CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
→‎Views: this one is important for canvas cameras actually: https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg11636.html
m (→‎Views: more best practices from osg-users)
m (→‎Views: this one is important for canvas cameras actually: https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg11636.html)
Line 95: Line 95:
With this approach you aren't creating/deleting graphics contexts, will
With this approach you aren't creating/deleting graphics contexts, will
lower memory usage and you'll get better performance.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg63061.html</ref>
lower memory usage and you'll get better performance.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg63061.html</ref>
Note: the slave osg::Camera aren't direct children of the View's
master osg::Camera, but they have their view and projection matrices
updated from the master camera.
Note II: osgViewer only threads Camera that are in the viewer, not
ones enclosed in the scene graph, so your Camera in Camera won't
thread.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg11636.html</ref>


* The right way to remove a view is outside of frame(). Not from an event handler from within the view, this will crash as you'll be deleting the object you are doing the work from.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg35639.html</ref>
* The right way to remove a view is outside of frame(). Not from an event handler from within the view, this will crash as you'll be deleting the object you are doing the work from.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg35639.html</ref>

Navigation menu