Steve -
I like your suggestion ... thanks.
-koko
On Apr 28, 2011, at 12:34 PM, Steve Christensen wrote:
> We're only supporting iOS 4.0 and later since we feel like there's sufficient
> adoption rate to make it worthwhile. Certainly if you feel like you still
> need to support pre-4.0, you could build against the current 4.x SDK, set the
> deployment target to be iOS 3.x (or whatever), and conditionally include the
> non-block animation code with a runtime check to handle each case. Putting a
> build-time conditional around the "legacy" code, and runtime check, means
> that it automatically gets compiled out when your builds stop supporting
> pre-4.0.
>
> #if __IPHONE_OS_VERSION_MIN_REQUIRED < __IPHONE_4_0
> if (![UIView
> respondsToSelector:@selector(animateWithDuration:animations:completion:)])
> {
> [UIView beginAnimations:...];
> ...
> [UIView commitAnimations];
> }
> else
> #endif
> {
> [UIView animateWithDuration:...];
> }
>
>
>
> On Apr 27, 2011, at 10:44 AM, koko wrote:
>
>> I am looking at the UIView Animations Overview.
>>
>> Block-based animations are recommended, but this iOS 4.
>>
>> Is it best to use begin/commit methods for compatibility !
>>
>> What are others doing?
>
>
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
