Re: [GEM-dev] pix buffer improvements

[Georg Holzmann]

Hallo again!

okay, I implemented now the stuff for pix_buffer_read and it performs much
much better (as fast as pix_image).

the changes:

o) check for new buffer: 
at start rendering and if the buffer is changed with a message

o) check for new image in the buffer:
at start rendering, when buffer changes, when index changes, in
auto-change-mode every frame of course

The only situation, where the behaviour differs is, when a new image is
loaded into a buffer - so you would have to retrigger the index now - is
that okay?

The new files are attached - if they are accepted I will also update the
help patches ...

LG
Georg

-- 
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pix_buffer_read.cpp
Type: text/x-c++src
Size: 6057 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20050824/a6676320/attachment.cpp>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pix_buffer_read.h
Type: text/x-chdr
Size: 2622 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20050824/a6676320/attachment.h>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pix_buffer_write.cpp
Type: text/x-c++src
Size: 5251 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20050824/a6676320/attachment-0001.cpp>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pix_buffer_write.h
Type: text/x-chdr
Size: 1847 bytes
Desc: not available
URL: <http://lists.puredata.info/pipermail/gem-dev/attachments/20050824/a6676320/attachment-0001.h>