Would it be useful to put the context info into the gemstate? This would possibly allow another language object to attach things to the context if the pointer and data are properly handled. It would also help with updating some of the Quicktime code which can move textures into a context directly.
<br><br><div class="gmail_quote">On Jan 16, 2008 3:33 AM, IOhannes m zmoelnig <<a href="mailto:zmoelnig@iem.at">zmoelnig@iem.at</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
it's like this<br><br>"gem_state 1" is sent whenever the rendering is turned on and triggers<br>the "startRendering"-method of each class.<br>"gem_state (pointer) (pointer)" triggers the actual rendering in each
<br>cycle; the actual gemstate (image-data, texcoords,...) is available in<br>the structure the pointer points to.<br>"gem_state 0" is sent whenever the rendering is turned off.<br><br>all of the above messages propagate through all gem-objects.
<br>turning rendering on/off is not the same as creating/destroying the<br>window (but probably you are fine with that)<br><br>i hope this helps.<br><br><br>mfga.sdr<br><font color="#888888">IOhannes<br></font><div><div></div>
<div class="Wj3C7c"><br>_______________________________________________<br>GEM-dev mailing list<br><a href="mailto:GEM-dev@iem.at">GEM-dev@iem.at</a><br><a href="http://lists.puredata.info/listinfo/gem-dev" target="_blank">
http://lists.puredata.info/listinfo/gem-dev</a><br></div></div></blockquote></div><br>