More related issues. Some of the compositions are merely a static image, possible scaled and shifted. These do not render at all when used in my subview, but do in the main view. The specs state that the composition will automatically play when the layer is installed in a visible layer hierarchy. This seems to be the crux of the problem. In my main view, they automatically play. In the subview, they do not, unless they have included some repetitive timing element. In the case of a static image, I assume ³play² means that the image should evaluate. I do not understand layer timing chains. What could possibly cause this difference between views?
The spotlight composition, previously mentioned, is a special case where I pass mouse position to the composition. On mouse down, I create and install the layer. It does not render unless I ding it again by moving (mouse dragged) or another mouse down at least one pixel different from initial position. It then renders properly. Again, the problem is getting it to render initially when installed. Another related issue I just ran into is that I realized that you don¹t get anything additional rendered unless something is continually changing. This showed up when I implemented a trail function. The trail fades with a fairly long time constant. Unfortunately, when I stopped moving the mouse, the trail fade stopped and remained in that state on the screen. To get around this, I introduced an imperceptible variation in the image position, driven by an LFO. This seems kind of wonky. Is there another way to keep the composition continuously rendering? On 3/7/13 3:25 PM, "Gordon Apple" <[email protected]> wrote: > 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.
_______________________________________________ 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]
