Thanks for the explanations Christopher. I'm reading through pg 15 of this to better understand the engine; http://developer.apple.com/mac/library/documentation/GraphicsImaging/Conceptual/QuartzComposerUserGuide/QuartzComposerUserGuide.pdf\
Can I just check that i've got this correct: Layers are always rendered sequentially to completion starting from the consumer backwards‚ all of layer 1, then all of layer 2, then all of layer 3 etc. (this goes for sublayers, etc) So if a Receiver exists in Layer 1, and the corresponding Sender exists in Layer 2, then the output of this receiver will be potentially unexpected. Because layer order cannot be changed by the composition, the Receiver will always know if it's at risk of being out of sync? If Rendering mode was set to bug-finding, could the entire patch be run twice, and differences in Send/Receive states be highlighted? Appreciate your time in answering what might be obvious questions. Keith On Thu, Jul 29, 2010 at 10:39 AM, Christopher Wright <christopher_wri...@apple.com> wrote: >> would writing "what he said" count as a valid bug report =] > > They're all "valid", it'd just get dup'd (if you're going to make an > intentional dup, at least include the original radar URL so it's easy for the > screener to tie them together without working too hard :) > >> also glad to see the buffer / hold last value idea isn't bunk. > > I mentioned that in my reply to Keith: > >> cwright said: >> The more fundamental problem is execution order -- if a broadcaster is layer >> 2, and a consumer that uses it is layer 1, it will always operate on 1-frame >> stale data (which could be wrong, and isn't entirely obvious). > > "1-frame stale" ~= sample&hold -- that's what spooky does today; it works, > but it can cause subtle problems (i.e. if you're passing around images for > filtering, some could filter the current frame, and others the previous > frame, and then compositing them together can be weird -- this can also be > used for artistic effect, of course :) > > -- > Christopher Wright > christopher_wri...@apple.com > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/quartzcomposer-dev/songcarver%40gmail.com > > This email sent to songcar...@gmail.com > _______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
