Errata for iPhone SDK Development

#43007: In the second last paragraph the instructions are confusing. You say, "When you release the mouse, as small HUD (What is a HUD, BTW) window will pop up ....... End the drag by releasing the mouse button.."

What actually happens is that the HUD does not appear until I release the mouse button after hovering over the FIle's Owner icon. It is then possible to hover over sayHello and select it by clicking again. After that,
not the method, but the File's Owner icon, flashes.
--David Millsom

#41990: In this example, we are linking the view in a xib file that we created ourselves for the first time. The oh-so-important line of text that tells the learner to make this connection is the last line of the 2nd paragraph. For people new to iPhone/Cocoa programming this is a HUGE deal and yet, it's given ONE line, one that could easily be missed.

I recommend expanding this line into a paragraph and bolding the text that tells the learner to hook this up. If it's missed, it will create headaches galore. If it's misunderstood, it's a big hole in the learner's mental picture of how all the pieces are fitting together.--Elisabeth Robson

#41992: I suggest clarifying at the bottom of the page that the *title* text field should be configured to capitalize words. The box office gross is a number so it doesn't matter, and the summary should be configured to capitalize sentences. So it's really only the title that should have this configuration. Some clarity here would be helpful.--Elisabeth Robson

#42433: The sentence states, "The interest-ing thing here is why choose viewDidLoad." This sentence reads wierdly and jarred me out of iPhone-land. Perhaps it would be better written as, "The interest-ing thing here is why we chose viewDidLoad."--Sean Mountcastle

#42300: I find the heading "4.8 Making the MovieEditorViewController" confusing since a previous section described the creation of that class and .xib file. Perhaps "Making the MovieEditorViewController instance", or "Launching the MovieEditorViewController", or "Connecting the two controllers", or...--David Ball

#45435: Noob question: In the last sentence on this page is there any particular reason to add the #import "Movie.h" to RootViewController.h rather than RootViewController.m? The header file doesn't seem to reference the Movie class and previously you'd recommended using @class in the header and #import in the implementation.--Bruce Hobbs

#45436: Another noob question: Doesn't the moviesArray instance variable mentioned in the second sentence of the first paragraph also need to be released in the dealloc method?--Bruce Hobbs

#45438: In the second sentence of the third paragraph you suggest adding the #import in the header file where previously you'd suggested using @class in the header and #import in the implementation. Shouldn't this be consistent?

#42264: Second paragraph ends with:

"The delegate adds the view defined by the tabBarController onto the window. Here is the code:

- (void)applicationDidFinishLaunching:(UIApplication *)application {
[window addSubview:tabBarController.view];
[self createData];
}

This code is straightforward; we just ask the tab controller. . ."

This is confusing to me as a newbie to iPhone programming. The default value in the file that was created for me by Xcode is:

<<
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {

// Add the tab bar controller's current view as a subview of the window
[window addSubview:tabBarController.view];
[window makeKeyAndVisible];

return YES;
}

>>

So now I'm confused about which one I need -- I'm moving ahead just adding the one you have in the book, but it would help to know that the exisitng one is ok too...
--Dave Colburn

#42265: Page starts with:
<<der of the data for the other states is created in the same way and added
to the same data array but not shown.1

NSMutableArray *data = [NSMutableArray array];
[data addObject:[NSDictionary dictionaryWithObjectsAndKeys:
[NSNumber numberWithInt:36553215], @"population" ,
@"California" , @"name" ,
[NSNumber numberWithInt:163770], @"area" , nil]];

After you create all the test data, you then need to set the states property
to the array you have just created. The code should look like this:
self.states = [NSArray arrayWithArray:data];
>>

<grrr> How 'bout consistency here??? I'm ok with you bending the paradigm of "here's the code, type it in" with regards to showing all the states (SUGGESTION: please use more than a footnote to indicate that you've bent the paradigm),

BUT, the last use of the code snippet
self.states = [NSArray arrayWithArray:data];

is breaking, not bending the paradigm. SUGGESTION: be very explicit about this one and tell us it's a code snippet you're showing...
--Dave Colburn

#41842: In loadprefs function, userTimeZone is assigned return value of method 'stringForKey' which is not alloc, new and copy but is released after simple assignment without retain call.

I think there should be some explanation about what happens behind the code. --Suhku Huh