Dirk Scheffter (scheff++at++ue.iff.fhg.de)
Fri, 17 Sep 1999 12:51:19 -0600
> I feel your pain. We have seen the exact same behavior when integrating
OpenGL
> widgets with performer. To get around it I not only do a glXMakeCurrent (Set
> the context when I enter the widget), but I also set the context to Null when
> I'm done with my widget function - glXMakeCurrent(getDisplay(), None, NULL).
> So, Performer doesn't munch on the OpenGl context I'm using for my OpenGL
> widget and and (I guess) is forced to get it's own. I'm not sure this will
fix
> your sigchild, but it's worth a shot.
Thanks, for your hint. I guess the SigChild was caused by
GLwDrawingAreaMakeCurrent() because this gets a widget as first argument and
widgets are not available in DRAW process (in the case of multi processing - a
typical shared memory problem.)
All my other GL widgets I'm drawing by OpenGL directly use
GLwDrawingAreaMakeCurrent() at beginning of each drawing because their
callbacks are called in APP proc.
Thus, it's not necessary to call glXMakeCurrent(getDisplay(), None, NULL) at
end of channel draw callback. But, it's of course another way to Rome... :-)
Thanks for your hint and have a nice weekend,
Greetings,
Dirk.
-- ----------------------------------------------------------- Dipl.-Inf. Dirk Scheffter scheff++at++iff.fhg.de Fraunhofer IFF fon: +49 (0) 391/40 90-854 Sandtorstr. 22 fax: +49 (0) 391/40 90-870 D-39106 Magdeburg http://wwwue.iff.fhg.de/~scheff Germany ----------< Try this: http://wwwue.iff.fhg.de/ibft/mowib >-
This archive was generated by hypermail 2.0b2 on Fri Sep 17 1999 - 03:53:18 PDT