Wade Olsen (wade++at++fnord)
Mon, 13 Dec 1993 17:11:34 -0800
I think a better way would be to place a structure in shared memory containing
all such info (e.g. wireframe mode, disable texturing, cursor shape). This
structure should be allocated before pfConfig (i.e. before performer forks
draw and cull processes) so all processes have a pointer to it. The
structure could also contain a counter that was incremented after any data
was changed. Then in the channel draw callback a local static counter can be
compared to see if something has changed.
Another option that I prefer is a little more complicated and addresses the
issue of GUI's in a different way. I have a Motif/Performer example where the
application process opens a window, creates the user interface, and handles all
events. The tricky part is some GLX code that allows the app process to
disconnect from the GLX widget and allow the draw process to connect to it.
This example works with performer 1.1 but should be easy to port to 1.2.
Wade
-- ------------------------------------------------------------------------------- Wade Olsen, wade++at++sgi.com, 415-390-1023, Silicon Graphics Computer Systems
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:07 PDT