On Mon, 16 Dec 2002, tigital wrote:
hello,
...I'm really not sure what or why IOhannes is doing some of these changes? So far, they have led to crashes and instability on the Mac OS X port. Thanks. I am frustrated, because things that worked no longer function correctly! What makes it worse is that these changes are done without any announcement or warning, unless you watch the cvs logs daily...and even then, the logs are not specific to changes in a file, and do not give any insight to the scope of the changes...
...the first problem came when IOhannes decided to rewrite the processImage() system: thankfully, he tried to hide most of this within #ifdef NEW_DUAL_PIX, but there was no discussion as to the thought behind this...
Ok, first, I think it might be a very good idea to announce such big changes. Not only will know what is goig to happen, but also the developer who does it gets a clearer idea about what is going to happen.
Better to wait a day for making the changes and going out for a beer, than spending some evenings on something that will prove not to work. (I know this is easy to say ...)
Guenter
...then he filed a rewrite of rendering:
deleted pix_fx the pix_fx functionality is now in GemPixObj this functionality is: save the image-state before it is processed and reconstruct it in the postrender function so we can change size/format and even bend the data-pointer and objects "before" will not notice (and crash)
...this is the cause of my crashes...previously, I could switch out movies on the fly when doing dual processing; now we get segfaults when there is no "old_data"...and this change was supposed to fix a crash? haha
...I don't see how Mac OS X support for GEM can continue without a little discussion before unilaterally making changes to cvs that affect all platforms...
l8r, jamie
PD-dev mailing list PD-dev@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-dev