None of this makes any sense, other than the build-transitions being one
level deeper in the hierarchy than the side transitions.
You're right. As I read the documentation over and over again it didn't make
any sense to me at all. First I thought it's the language, since my mother
Here's the current status. I seem to have everything working, partly
due to you guys. Thanks. However, now having analyzed this thing to death,
I'm filing a bug report.
First a summary of the (extended) problem. The view is layer hosted.
Its layer has a sublayer called content, which
On Sun, 15 Nov 2009 22:38:04 -0600, Gordon Apple g...@ed4u.com said:
What I don't understand, is that, according to the core animation guide,
kCATransition seems to be what I want for a key instead of sublayers. The
guide says this is triggered by replaceSublayer: with:. However, stepping
it
On Mon, Nov 16, 2009 at 9:23 AM, Matt Neuburg m...@tidbits.com wrote:
On Sun, 15 Nov 2009 22:38:04 -0600, Gordon Apple g...@ed4u.com said:
What I don't understand, is that, according to the core animation guide,
kCATransition seems to be what I want for a key instead of sublayers. The
guide
OK, straight out of the core animation guide section on Layer Actions:
The CALayer class provides default action objectsinstances of CAAnimation,
a CAAction protocol compliant classfor all animatable layer properties.
CALayer also defines the following action triggers
On Mon, 16 Nov 2009 10:25:07 -0800, Kyle Sluder kyle.slu...@gmail.com
said:
On Mon, Nov 16, 2009 at 9:23 AM, Matt Neuburg m...@tidbits.com wrote:
On Sun, 15 Nov 2009 22:38:04 -0600, Gordon Apple g...@ed4u.com said:
What I don't understand, is that, according to the core animation guide,
On Mon, Nov 16, 2009 at 11:01 AM, Matt Neuburg m...@tidbits.com wrote:
Nothing here runs contrary to the documentation. We're now talking apples
and oranges. The key used in addAnimation:forKey: (such as kCATransition)
has nothing whatever to do with the key that arrives in
On Sat, 14 Nov 2009 14:58:31 -0600, Gordon Apple g...@ed4u.com said:
I assume this should be simple, but so far I haven't found the magic
incantation, even after reading the docs, Dudley's book, and some archives.
Problem: Layer called contentLayer has sublayers containing layer A,
which is
On Sun, Nov 15, 2009 at 6:51 PM, Matt Neuburg m...@tidbits.com wrote:
Your understanding is likely wrong. :) addAnimation:forKey: on a layer
triggers the animation then and there. Look at the examples in the Animation
section of the Core Animation Programming Guide.
To elaborate, the purpose
On Sun, Nov 15, 2009 at 8:27 PM, Kyle Sluder kyle.slu...@gmail.com wrote:
aLayer.actions = [NSArray arrayWithObject:anAnimation];
Er, this is supposed to be a dictionary, not an array. But you
probably noticed that or would have understood the compiler error.
Sorry 'bout that.
--Kyle Sluder
I had actually tried using that delegate method. It gets called a lot
because the same controller is delegate to many layers (for drawing). Of
course, I filter it for the my content layer. As you noted, using
sublayers also triggers for other sublayers and I may have to use your
flag method
I assume this should be simple, but so far I haven't found the magic
incantation, even after reading the docs, Dudley's book, and some archives.
Problem: Layer called contentLayer has sublayers containing layer A,
which is to be transitioned to layer B. (Note: Using GC here.) Controller
12 matches
Mail list logo
