Hi Martin, AdapterWidget using GraphicsWindowEmbedded to enable osgViewer to reuse an already create OpenGL context, this route is easy to implement, but and it's a big but, it doesn't integrate any of the high level context management that multi-threading or switching between contexts requires - this means you can only use it in places where you have a single viewer per window.
For a fully capably viewer you need to use QOSGWidget which uses osgViewer itself to create and manage the graphics context, but using QT to create the window. This route allows the Viewer/CompositeViewer to handle multiple contexts and multi-threading. Robert. On Mon, Sep 29, 2008 at 11:48 PM, <[EMAIL PROTECTED]> wrote: > I'm a little confused about the difference between AdapterWidget and > QOSGWidget. > > As far as I can see AdapterWidget derives from QGLwidget and so should > be a drop in replacement in any opengl sample. > But QOSGWidget is a QWidget and so can be used directly in a mainwindow. > > Are there any other performance/capability differences between them? > Which should be the starting point for a new application on QT4 > > Thanks > Martin > > > > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
