code

Xcode has long been installed in the /Developer folder on the Mac. The introduction of Xcode 4.3 in the App Store moved that to /Applications/Xcode.app. Fix behavior for some of those apps that rely on that hardcoded path.

The problem arises that one view controller is portrait (or landscape) only, and everything else can be rotated. Then when navigating to that one controller, the view is incorrect and it tries to display in landscape... to undesired results. There is a solution!

ActionScript, Java, and most other ECMAscript-based languages (even javascript) have an easy way to define variables as protected or private. Objective-C does not have a simple way to do so, at least when based on the recommended ways to create variables.

Implementing rotation in a UIViewController is simple because Apple provides methods at any number of points to ensure animation is crisp. Rolling your own in a UIView is easy to set up, however it is far less robust. This will show how to handle orientation change for your iOS device.

UIViewControllers are great for displaying and managing views. However, I find that once memory issues come into play, the experience can degrade. Also, memory management with the didReceiveMemoryWarning and viewDidUnload methods do not have any best practices in the Apple documentation. This is an example of how to provide a consistent experience utilizing the built–in memory methods in a UIViewController.