Hi Christoph,

thank you for your fast reply. I hope you don't mind that it took me
quite some time to answer. I tried your suggestion and build my own
qt4-Widget analog to the OpenSG qt4 Widgets. I build something similar
once with qt3, but this time with qt4 it didn't work. I had the same
problem as before with the passive window. I render the passive window
and the MultidisplayWindow inside the qt callback. I don't have any idea
where else I should be rendering the passive Window instead.

Actually, since we needed a solution, we skipped qt4 completely, and
used a GlutWindow instead. I am not sure if there is an incompatibility
with qt4, OpenSg and MultidisplayWindows or not. But if there is no one
right now who is reading this mailing list and has a working application
using such a setup, I wont be trying that again for the moment.

Thanks again
Lennart

> Hi Lennart,
>
> I remember I once had a similar Problem. Back then I tried to render
> the passive window by an external thread (not the one osg::init() was
> called in) - don't know if this is the case with you? The trick was
> not to use the passive window but to use the Qt window provided by
> OpenSG.
> 
> Cheers,
> Christoph
>
> > Hello everyone,
> >
> > I am having a problem using Passive Windows within a Qt4 OpenGL Widget.
> > I wrapped a setup for a cave rendering in a class that is derived from
> > the SimpleSceneManager in order to leave the interface of the Manager
> > intact.
> >
> > I use the SimpleSceneManager's OSGWindow-member  and define an
> > additional MultidisplayWindow, with no assigned client window. The setup
> > includes an own Viewport and Perspective Camera for the local window of
> > the SimpleSceneManager, in this case the Passive Window used within qt4,
> > and StereoBufferViewports together with ProjectionCameraDecorators,
> > which are wrapping a second PerspectiveCamera. All viewports use the
> > same scenegraph for rendering. I can assign two aspects, but right now I
> > use the same aspect for both window-members.
> >
> > The problem is that the application wont show the client window at all
> > and doesn't render the images on the remote clients. All socket
> > connections are established but the application is hanging in the
> > display callback of the qt widget, which is called only once and doesn't
> > finish. This is a call stack of the lock:
> >
> > #0  0x00007fced7199d73 in select () from /lib/libc.so.6
> > #1  0x00007fcedafb3d3a in osg::SocketSelection::select ()
> > from /usr/lib/libOSGBase.so.1
> > #2  0x00007fcedafa677a in osg::GroupSockConnection::wait ()
> > from /usr/lib/libOSGBase.so.1
> > #3  0x00007fcedbd089cc in osg::MultiDisplayWindow::clientSwap ()
> > from /usr/lib/libOSGSystem.so.1
> > #4  0x00007fcedbcd1481 in osg::ClusterWindow::render ()
> > from /usr/lib/libOSGSystem.so.1
> > #5  0x000000000040761a in OSGWidgetManager::paintGL
> > (this=0x7fff3e6e3380) at OSGWidgetManager.cpp:46
> >
> > We have about a handful of applications running with this
> > OSG-Cluster-Wrapper-setup without problems, with GLUT-Windows or
> > X-Windows. I wrote an additional Passive-Window test with a GLUT OpenGL
> > context and that one is working too.
> >
> > Does anyone of you have an idea what might be the problem here or has
> > experienced something similar?
> >
> > Thanks in advance!
> > Lennart
> >
> >
> > ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > Opensg-users mailing list
> > Opensg-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/opensg-users
> >




------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to