I am not doing that to my knowledge. Here is my creation code:
CALayer* rootLayer = [ self layer ];
NSString* compositionPath = [ [ NSBundle mainBundle ]
pathForResource: @"information" ofType: @"qtz" ];
mStatusLayer = [ [ QCCompositionLayer compositionLayerWithFile:
compositionPath ] retain ];
mStatusLayer.frame = NSRectToCGRect( [ self bounds ] );
mStatusLayer.autoresizingMask = kCALayerWidthSizable |
kCALayerHeightSizable;
[ rootLayer addSublayer: mStatusLayer ];
The only other thing is hiding and showing the layer.
Another oddity is that the Particle System starts with a bunch of
particles showing in the QCCompositionLayer but starts with none in
QC.app.
On Mar 1, 2009, at 5:21 PM, Troy Koelling wrote:
Are you modifying the time on the layers in any way? Using the patch
in non perlin mode is the legacy mode, only exists for backwards
compatibility. It doesn't do well in iterators, or any situation
where you have externalized the timebase.
For those who write your own plugins, here's what to watch out for:
There is an ivar which tracks the state from frame to frame in the
old random algorithm. When the time passed a threshold, the ivar is
updated. But if the patch tim is negative or modified multiple times
per frame inside an iterator, that can get really messed up. Now
there is a lookup function and Random using perlin is little more
than the Noise patch where x is tied to time.
_______________________________________________
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]
