Hi, Gerrit Voss schrieb: > Hi, > > On Wed, 2009-02-11 at 11:26 +0100, Christoph Schäfer wrote: > >> Christoph Schäfer schrieb: >> >>> Hi, >>> >>> >>> >> I just noticed MyOSGQGLWidget::initializeGL actually is called by Qt via >> it's parents by QGLWidget::initializeGL. Depth testing doesn't seem to >> work anyway, the problem described above persists. Oh and forget about >> this blue background question - I set it to blue myself ;-) >> > > ok, my 'is not called' was slightly off, it's called but the effects are > hidden. From a quick look at it, initializeGL setups the OpenSG created > context whereas paintGL uses the QT generated one. So one solution is > to add osgWin->activate() before frameInit. But that is rather overkill > as you constantly flip through the OpenSG and QT context. > > The solution should either be, use the QT context and be happy, > otherwise convince QT to drop it's context and use the one from OpenSG, > but one of them should go. > > kind regards, > gerrit > > Ah ok! I sneaked into it with gedebugger and noticed the two contexts but didn't manage to figure out which command goes to which context.
So there is basically one questen - Which context is supposed to be used? I thought the OpenSG context has to be used and the calls to the Qt context must be redirected to the OpenSG context by the OSGGLWidget? Cheers, Christoph ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
