Re: Using custom inputExtent for Core Animation transition

On Sep 20, 2009, at 7:30, Adam R. Maxwell wrote:

>
> On Sep 19, 2009, at 4:01 PM, Christiaan Hofman wrote:
>
>> Thanks, I was afraid that was the answer. Anyway, I've given up on  
>> CA for now anyway, because performance on 10.5 is unacceptable (see  
>> my other message). So I'm going back to what I did using more  
>> explicit animations using NSAnimation, which gives me full control  
>> over the filter input, and moreover gives me better performance on  
>> 10.5 (believe it or not).
>
> I believe it.  I tried using it for a fairly simple crossfade view  
> transition and gave up; IIRC calling setWantsLayer: on my tableview/ 
> outlineview gave unacceptable ghosting when scrolling, but was the  
> only way to get a reasonable transition.  Even worse, it can screw  
> up the NSUIHeartBeat thread on 10.5:
>
> http://www.cocoabuilder.com/archive/message/cocoa/2009/1/8/227043
> http://www.cocoabuilder.com/archive/message/cocoa/2009/8/20/243038

That's not even the biggest problem, as that can be overcome by only  
setting wantsLayer to YES temporarily during the animation. For me  
it's just that on 10.5.8 CA drops too many frames for complex  
transitions like CIPageCurlTransition, as well as the fact that it  
gives far too little control over the settings. I thought CA was  
supposed to be more efficient, but it isn't.

Christiaan