Re: replacing NSViewAnimation with CoreAnimation
Re: replacing NSViewAnimation with CoreAnimation
- Subject: Re: replacing NSViewAnimation with CoreAnimation
- From: Scott Anguish <email@hidden>
- Date: Wed, 21 Nov 2007 17:17:31 -0500
On Nov 21, 2007, at 4:05 PM, Christoph Vogelbusch wrote:
Well the problem/question is:
Is NSViewAnimation SLOWER then CoreAnimation (because it uses no
layers).
If so I would use NSViewAnimation for Tiger and CoreAnimation for
Leopard.
But there is no reason why Apple didn't rewrite some of the
NSViewAnimation code for Leopard. I'm technically it's teh same
thing I'm doing here. Intercepting ViewAnimations put them in a
animation context and fire them together.
SO the Question is: Is NSViewAnimation under Leopard as fast as
CoreAnimation (and uses layers) or not?
As Nick said NS*Animation isn't related to Core Animation.
View animation has never had a goal of running at a specified number
of frames per second as far as I know. Core Animation on the other
hand...
View animation is intended for resizing or moving views around in a
UI, not animating all sorts of bits.
That said, no I don't believe it has been rewritten to use Core
Animation. I doubt that NSViewAnimation changed at all to use the
animatable properties support (which is where this would have migrated
to, had it migrated.. not to Core Animation).
But the person who could definitively say isn't likely to read this
message this week what with Thanksgiving and all (or perhaps ever,
since there is no guarantee that anyone at Apple will read anything on
the list)
Of course if you really want to know if it uses it you could always
use the debugging tools.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden