Sounds like some good changes.
I like very much the possibility of having more control over the render buffers (as I do a lot of single buffering)
In terms of gemwin clearing, there is a bang method already there that clears?
Ben
On Sunday, April 6, 2003, at 07:17 PM, Daniel Heckenberg wrote:
I've made a couple of changes to GEM CVS:
(all) added "render" message to [gemwin] to force a single frame rendering right away (all) allowed "frame 0" to [gemwin] to set the automatic frame rate to 0 (win only) added "topmost" message to make gem window stay on top (win only) added VC++7 workspace and project (win only) fixed pix_film initial frame crash and changed pix_film to be more robust
ToDo: incorporate pix_filmNT changes into the pix_filmNEW object (filmAVI).
Things to discuss: -It would be very handy to be able to share uploaded textures across gem lists in a similar way to the pix sharing mechanism. This should be easy to implement.
- I'm going to implement some control over window clearing into gemwin.
This can be used to do multipass rendering and various other things. I'm proposing a couple of changes:
- "clearmode f" message to [gemwin] to set which buffers are cleared
automatically in each render cycle
- [clear] object to be inserted into the rendering chain to force a
clear at that time.
It could be argued that a "clearnow" message to the [gemwin] would be more appropriate since the clearmessage forces a global change. What do you think?
Daniel
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev