Thanks Steve, that's exactly what I needed to know. Thanks for all the quick responses guys.
On Tue, Feb 2, 2010 at 1:40 PM, Steve Mokris <[email protected]> wrote: >> The clear patch helped in a lot of the cases. Is this just a bug in >> quartz composer? > > No, it's not a bug, it's intentional behavior. The buffer is not cleared by > default in Render In Image. This is presumably a performance optimization > (don't clear the buffer unless you know what you want to set the values to, > otherwise you probably end up clearing the buffer twice, wasting precious > write bandwidth), as well as facilitating the Feedback Rendering feature. > > (The main viewer buffer behaves similarly --- go to the Viewer menu, click > "Disable Background Erasing", and watch what happens when you resize the > viewer window.) > > >> It seems like it's reading uninitialized data, or something it shouldn't >> have access to. > > Yes, it's reading uninitialized data, but no, this isn't a security hole. > The worst you can do is display onscreen something in VRAM that's left over > from a previous use of VRAM (which was probably displayed onscreen anyway). > Safe Mode restrictions (in effect when, for example, viewing a composition in > Safari) prevent the image data from being used for anything other than > displaying onscreen. > > >> Do other people see the same issue? > > Yes, this effect occurs on every hardware and software configuration I've > seen. > > > Steve > > -- > Steve Mokris [ [email protected] ] > http://kineme.net/ > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
