iOS 编程陷井.

作者:不及格的程序员-八神

•  要注意不支持的特性

    比如你的手持设备不支持发送短信或邮件的话,创建该类型的类时将返回nil...,这与我们平常习惯性的理解不同,如果是我设计我会让它抛出异常可能会更好,至少不需要查api文档就知道怎么回事。

•  设备的方向

    当你在window上连续添加两个景色模式的视图控制器的时候,第二个视图的方向会保持人像模式,并且它的shouldAutorrotateToInterfaceOrientation方法不会被触发...

•  根视图中的输出口

   这个算不算,可以根据开发人员的个人理解而定,按传统编程想法,当从nib文件实例化一个视图控制器时,我觉得视图中的所有输出口控件都会自动初始化,但是苹果的模式不是,它需要激发根视图view属性,确认将下面的所有子视图连接到输出口上.

•  在烦忙的工作开始之前,先播放动画

   这又是一个苹果模式,如果你想在下载文件的时候同时播放等待动画,如果你先去执行(注意是直接执行而不是延时执行)下载代码,那么前面的动画将在烦忙的代码执行完毕后播放,显然不是我们要的.

[activityIndicator startAnimating];
[self performSelector:@selector(someMethod) withObject:nil afterDelay:0.0];

这是苹果关于屏幕旋转问题的答QA,里面也说了window仅支持第一个视图的旋转....
Technical Q&A QA1688 Why won't my UIViewController rotate with the device? Q: Why won't my UIViewController rotate with the device? A: Why won't my UIViewController rotate with the device? There can be several possible reasons your view controller does not rotate. The UIViewController class provides the fundamental view-management model for iPhone applications. It provides automatic support for rotating the views of the view controller in response to changes to the orientation of the device. If the autoresizing properties of your view and subviews are properly configured, this behavior is essentially free. Your view controller may not rotate in certain situations if: The view controller does not implement this delegate method: - (BOOL)shouldAutorotateToInterfaceOrientation:(UIInterfaceOrientation)interfaceOrientation; Even if shouldAutorotateToInterfaceOrientation is implemented, you should make sure it returns YES for all the orientations you wish to support. To support all orientations, simply always return YES. The view controller's UIView property is embedded inside UIWindow but alongside an additional view controller. You may find a situation where shouldAutorotateToInterfaceOrientation is called once at startup for a given view controller but is never called again when the device is rotated. Because view controllers are tightly bound to the views they manage, they are also part of the responder chain used to handle events. View controllers are themselves descendants of the UIResponder class and are inserted into the responder chain between the managed view and its superview. So it is common practice to have one primary view controller in your application as part of the responder chain. You would typically add one primary view controller such as a UINavigationController, UITabBarController or a generic UIViewController to your UIWindow. For example, this is done by calling: [myWindow addSubview:primaryViewController.view]; If you add an additional view controller's UIView property to UIWindow (at the same level as your primary view controller) via the following: [myWindow addSubview:anotherController.view]; this additional view controller will not receive rotation events and will never rotate. Only the first view controller added to UIWindow will rotate. Note: You may add one view controller's UIView property as a subview to another view controller. In doing so, both views will rotate but the parent view controller remains in charge of determining the supported orientations via its shouldAutorotateToInterfaceOrientation method. Note: Keep in mind that UINavigationController and UITabBarController have the capability to manage a "stack" or "list" of view controllers on their own. You have added your view controller's UIView property to UIWindow as a subview, but prematurely released it soon after. UIWindow will retain that view, but not the view controller itself. You must not release it prematurely. Declare it as a "retainable" property in your UIApplicationDelegate subclass. Note: UINavigationController and UITabBarController retain your view controllers, so you can release them once they have been added. All child view controllers in your UITabBarController or UINavigationController do not agree on a common orientation set. To make sure that all your child view controllers rotate correctly, you must implement shouldAutorotateToInterfaceOrientation for each view controller representing each tab or navigation level. Each must agree on the same orientation for that rotate to occur. That is, they all should return YES for the same orientation positions. Overriding the -(id)init: or -(id)initWithNibName:(NSString *)nibName bundle:(NSBundle *)nibBundle method without calling super. For the object to be initialized properly, you must call super on any init or initWithNibName method you are overriding for your view controllers.