Always happens after I post something. While Googling to find out what the “tension” parameter was for in the Interpolator, I accidentally found out about control-clicking the patch bar for other options. Setting the timing to “local” (vs. the default “parent”) seems to have solved the problem. I still don’t understand why this performed differently in one view vs. another. The non-performing view was actually a subview of the performing one. It must have something to do with the timing distribution chain in the view/layer hierarchies. Wow! Really obscure.
On 3/7/13 2:00 PM, "[email protected]" <[email protected]> wrote: > I have some simple compositions that are will not run in one of my views if > not in loop mode. The simplest case is a (3/8 in.) circle image which ramps > down to a few pixels radius. I¹ve tried this with a circle patch and with a > circle image. They run just fine in the viewer, the finder, and in another of > my views. However, in one view, playing in a simple subclass of > QCCompositionLayer, they will run when the composition¹s interpolators are in > loop mode, but not in non-loop mode. They just appear in their final state > when the (newly created) layer is installed. Could there be something missing > here in the view or layer hierarchy that should reset and kick-start the > process?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
