Comments on: iPhone SDK 3 and Deprecated Method Warnings http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html iOS Developer Tips, Tricks and Tutorials. Wed, 08 Feb 2012 06:31:16 -0600 hourly 1 http://wordpress.org/?v=3.3.1 By: Simon http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html#comment-24019 Simon Wed, 25 Aug 2010 11:45:51 +0000 http://iPhoneDeveloperTips.com/?p=2499#comment-24019 Yes you can include 3.0 SDK features in a build with a deployment target of 2.2.1. You have to weak link the 3.0 library. And you have to make sure that you don't call any 3.0 api's on a 2.2.1 device. Apple have a sample app that shows you how. http://developer.apple.com/iphone/library/samplecode/MailComposer/Introduction/Intro.html Yes you can include 3.0 SDK features in a build with a deployment target of 2.2.1. You have to weak link the 3.0 library. And you have to make sure that you don’t call any 3.0 api’s on a 2.2.1 device. Apple have a sample app that shows you how.

http://developer.apple.com/iphone/library/samplecode/MailComposer/Introduction/Intro.html

]]> By: John Muchow http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html#comment-4858 John Muchow Mon, 07 Sep 2009 05:03:09 +0000 http://iPhoneDeveloperTips.com/?p=2499#comment-4858 Chris, iPhone apps are targeted for one base platform. For example, if you create a build for 2.2.1, you typically do not include features of the 3.0 SDK, one way around this is weak linking, see Simon's comment. John Chris,

iPhone apps are targeted for one base platform. For example, if you create a build for 2.2.1, you typically do not include features of the 3.0 SDK, one way around this is weak linking, see Simon’s comment.

John

]]> By: Chris http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html#comment-4857 Chris Mon, 07 Sep 2009 02:38:47 +0000 http://iPhoneDeveloperTips.com/?p=2499#comment-4857 So do you release two different versions of your app, one for = 3.0? Or do both of these get put into a "universal binary" for the iPhone? So do you release two different versions of your app, one for = 3.0? Or do both of these get put into a “universal binary” for the iPhone?

]]> By: Marco Lazzeri http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html#comment-4121 Marco Lazzeri Wed, 22 Jul 2009 09:03:37 +0000 http://iPhoneDeveloperTips.com/?p=2499#comment-4121 Great hint! Thanks Great hint! Thanks

]]> By: Wim Verhoef http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html#comment-4041 Wim Verhoef Sat, 11 Jul 2009 13:04:10 +0000 http://iPhoneDeveloperTips.com/?p=2499#comment-4041 Mike, If you are targeting an SDK prior to 3.0 the preprocessor variable __IPHONE_3_0 is undefined so the else part is used. Now if you are compiling for an SDK equal to or after 3.0 the variable WILL be defined so the then part is used. No need to do a comparison. To check how this works just have a look at Availablity.h in the SDK. As you see all previous versions are defined as well: #define __IPHONE_2_0 20000 #define __IPHONE_2_1 20100 #define __IPHONE_2_2 20200 #define __IPHONE_3_0 30000 #define __IPHONE_NA 99999 /* not available */ If you really want to do a comparison, the comments in Availability.h recommend this: #if __IPHONE_OS_VERSION_MIN_REQUIRED >= 30000 // code for OS3.0 and later #else // code for earlier versions #endif Mike,

If you are targeting an SDK prior to 3.0 the preprocessor variable __IPHONE_3_0 is undefined so the else part is used. Now if you are compiling for an SDK equal to or after 3.0 the variable WILL be defined so the then part is used. No need to do a comparison.
To check how this works just have a look at Availablity.h in the SDK.
As you see all previous versions are defined as well:

#define __IPHONE_2_0 20000
#define __IPHONE_2_1 20100
#define __IPHONE_2_2 20200
#define __IPHONE_3_0 30000
#define __IPHONE_NA 99999 /* not available */

If you really want to do a comparison, the comments in Availability.h recommend this:

#if __IPHONE_OS_VERSION_MIN_REQUIRED >= 30000
// code for OS3.0 and later
#else
// code for earlier versions
#endif

]]> By: Mike Weller http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html#comment-3784 Mike Weller Fri, 03 Jul 2009 14:44:56 +0000 http://iPhoneDeveloperTips.com/?p=2499#comment-3784 I've been using similar code, but my problem is this: what happens when the version goes up to 3_1? Now that code is going to revert to the pre 3.0 version. Is there some way to do a "if version < 3" test? I’ve been using similar code, but my problem is this: what happens when the version goes up to 3_1? Now that code is going to revert to the pre 3.0 version. Is there some way to do a “if version < 3″ test?

]]> By: Maksim Horbul http://iPhoneDeveloperTips.com/cocoa/iphone-sdk-3-and-deprecated-methods.html#comment-3633 Maksim Horbul Tue, 30 Jun 2009 07:17:03 +0000 http://iPhoneDeveloperTips.com/?p=2499#comment-3633 The most often met deprecation warning is related to the cell.text. UITableViewCell in SDK 3 offers textLabel and detailTextLabel: #if __IPHONE_3_0 cell.textLabel.text = @"The Text"; cell.detailTextLabel.text = @"The Sub-text"; #else // cell with the custom content view cell.text = @"The Text" cell.customSubTextLabel = @"The Sub-Text" #endif <em>Editor's note: cell.customSubTextLabel does not exist in 2.x. To have functionality similar to the 3.0 cell.detailTextLabel, you would have to add a custom label to a subclass of cell.</em> The most often met deprecation warning is related to the cell.text.

UITableViewCell in SDK 3 offers textLabel and detailTextLabel:

#if __IPHONE_3_0
cell.textLabel.text = @”The Text”;
cell.detailTextLabel.text = @”The Sub-text”;
#else
// cell with the custom content view
cell.text = @”The Text”
cell.customSubTextLabel = @”The Sub-Text”
#endif

Editor’s note: cell.customSubTextLabel does not exist in 2.x. To have functionality similar to the 3.0 cell.detailTextLabel, you would have to add a custom label to a subclass of cell.

]]>