While I think some of these are good ideas relating to pix_buffer, none of them strike me as something which can only be done on the C code level or would pose some great advantage by doing it there - the possbile exception might be the clearing code. Loading and saving images can be done on the patching level using existing objects.
<br><br>I have no idea what you would do with a gemlist written to a file. It doesn't strike me as something that would be useful for later apart from possibly debugging. What is your reasoning behind this request?<br><br>
cgc<br><br>On 2/22/06, <b class="gmail_sendername">B. Bogart</b> <<a href="mailto:ben@ekran.org">ben@ekran.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hey all,<br><br>So I've been working a lot with the pix_buffer (depot) stuff and had a<br>few ideas that would make using it even more useful:<br><br>* The ability to colour the buffer black, effectively clearing it<br>without deallocating memory.
<br><br>* The ability to load and save the images in a buffer, basically being<br>able to take a snapshot of the system so that the same images that were<br>in the buffers can be reloaded, restoring the original state.<br>
<br>* It would be also nice to be able to save a particular frame rather<br>than the whole buffer.<br><br>"load [filename]"<br>to pix_buffer_read could load the [filename] into the slot already set<br>by the pix_buffer_read index. "load [wildcard] 10" would load 10 images
<br>matching the wildcard pattern into 10 slots (reallocate if needed?)<br><br>"save [filename]" to pix_buffer_write would save the image in the<br>current slot to that filename. "save [filename] 10" could save images
<br>from the first 10 slots to filename with an id appended: "file0000",<br>"file0001" etc..<br><br>"clear 10" or "clear" to pix_write would clear the first 10 slots, or<br>the current slot respectively. "black" may work instead of the word
<br>"clear".<br><br>Oh and It would be amazing if you could put pix_write in a gemchain and<br>have it only capture that gemlist in the buffer... or maybe the current<br>pix_write should be called something like window_write since it does not
<br>actually save what is happening in the pix_ of a chain...<br><br>Thanks!<br><br>.b.<br><br><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">http://lists.puredata.info/listinfo/gem-dev</a><br><br><br><br></blockquote></div><br>