Hi, Robert: > is there a reason why this rather than 1,1,1,0? No reason. I thought this would make no difference.
>The default setting attribute Qt::WA_TransparentBackground does make >me a bit uneasy, what is users don't want a transparent background? >This is something that we should probably provide control of. I agree. > It would also be good to put together an example that implements a > basic UI such as in your examples. This could possible by a test bed > for experimenting with different ways of integrating OSG/Qt. OK, I'll whip something up over the weekend. Skylark: > The direction you're taking in the Delta3D forum thread seems to be more > of a dead end to me, since it forces Qt and OSG to run single threaded. I haven't yet managed to get OSG and Qt running in different threads. The whole interplay of windows and GL contexts and so on is new to me and pretty confusing. Are there any running examples where a Qt widget contains an OSG window that runs in a different thread? Next I will look at combining osg and qt with the use of frame buffers. I think it would be less complicated to render OSG output to a frame buffer and display that in the Qt thread. This way we can use the Qt event loop and be sure that the mouse and keyboard events are correctly handled. Any thoughts? Another thing: I'm pretty much an OpenGL n00b, so excuse the ignorance. What is the most efficient way to get the OpenGL output of one thread into the OpenGL scene of another thread? Can I somehow reuse the frame buffer of one gl context in another context? Or do I have to download the frame buffer to main mem and then re-upload it to the graphics mem? Martin ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=28112#28112 _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
