enjoying working with your book.

found a small problem using the iphone in Unnamed Chapter page 24/28 4.94% into book or pdf book page 43

line 4 of the code runs of the screen in portrait and landscape as shown below

- (void) sayHello: (id) sender {
NSString* userName = nameField.text;
NSString* helloMessage =
[[NSString alloc] initWithFormat: @"Hel
helloLabel.text = helloMessage;
[helloMessage release];--Gary McWilliams

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

The screenshot on page 47 shows the placeholder text as "Type your name", however, on page 45, the placeholder text is "Name", as is the example text in the first sentence on that page.--Yogi Patel

Last sentence of the penultimate paragraph: "…load the application from a nib file." Don't you mean obtain obtain the values for the third and fourth parameters (application's main class and its application delegate) from a nib file?--Bruce Hobbs

Line [formatter setNumberStyle:NSNumberFormatterCurrenctyStyle];
results in an empty string return from numberFromString (self.movie.boxOfficeGross hold empty string).

--Gabriel Doroftei

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

Shouldn't the fifth sentence of the first paragraph begin, "Assigning to self what…?" Would also seem helpful to include at least some explanation of the reason for this assignment.--Bruce Hobbs

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

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

MovieViewController.m MUST have the following line however I cannot find a mention of this anywhere:
@synthesize editingViewController;--David Swearingen

Section 4.6, first sentence, reads: "Let’s now create a second view controller that we will use to manage the modal view." I think that should be *model* view, not modal view.--Marc Hedlund

Section 4.7 first screen shot from IB shows the incorrect class for the file's owner of the MovieEditorViewController. It shows Class set to MoveViewController instead of MovieEditorViewController. I figured it out from reading the text again after my expected outlets were missing..--Bill Dennis

UITableViewCellStyleValue1 and 2 descriptions say they are intended only for use in group-style tables. Why is that? They seem to work ok in plain tables. And... on the next page, they are shown in Figure 5.4 in a plain table! If they aren't appropriate for plain tables, they shouldn't be shown as an example.--slothbear

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

There is a bug in the source code for chapter 5
Bug: Memory Leak
File: <base>/TableViews/MovieTabler02/Classes/RootViewController.m
Line: 56
Desc:

moviesArray = [[NSMutableArray alloc] init];

This is allocated but never released... --Steve McFarlin

First, in the last paragraph, "You might recall from Section 5.2 ... that in MainView.xib ...". There is no MainView.xib--this should be MainWindow.xib.

Second, this sentence doesn't make any sense in context, at least with SDK 3.2: "Then, on the right side of this assignment, notice the reference to self.editButtonItem." The context is that we are examining properties of UINavigationItem, and I can find nothing about self.editButtonItem in the right-click popup for this object or in the inspection palette. Either there is some text missing, or the SDK has changed since this bit was written.--Ben Fulton

The book states "Add an instance variable MovieEditorViewController* movieEditor;"

The code has the asterisk prior to "movieEditor;" thusly "*movieEditor;"

The same is true of this statement "Movie *editingMovie;" but I couldn't find the page with the instruction that states "Movie* editingMovie;"--Ralph Barhydt

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

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

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?

In the section "Loading and Using a Custom Table Cell", 3rd line: the phrase "...we try to fail to dequeue..." is confusing. Did you mean just "we fail to dequeue"--John Tarcza

The example code has an 'initWIthFrame:CGRectZero', which according to page 84, has been depricated for iPhone SDK 3.0. It should read 'initWithStyle:UITableViewCellStyleDefault'.--Adam Findley

Both picture and the text on p. 118 show that Table View for RootViewController has a navigation bar, however that's not what I see in XCode 3.2.1 (iPhone OS 3.1.3) - it's just a table, with no Navigation bar.--Victor Kryukov

In the last paragraph it says: <br>
"Right-click the Classes group in Xcode, and choose Add > New File.
Choose to make a subclass of UITableViewController (select Cocoa Touch
Classes -> Objective-C class and then UITableViewController from the
pulldown), click Next, and then name your new controller DVDCabinet-
Controller."
<br>
YARRRRGGGHHHH the previous comment is right. Just create a UIViewController subclass -- yes, I know to the already informed that this may seem obvious, but to someone just learning it's frustrating!!!!
--Dave Colburn

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

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

I use the latest 3.1.3 iPhone SDK on the latest Snow Leopard version. There, the creation of a "UITableViewController" subclass has changed: The book says to select "Objective-C class" and then select "UITableViewController" in the subclass pulldown. In my Xcode version, "UITableViewController" isn't in that dropdown anymore. Instead, you need to select "UIViewController subclass" and then check the "UITableViewController subclass" checkbox. There you can even create the XIB file in the same step.--Karsten Silz

I needed to explicitly connect the delegate and dataSource outlets on the TableView that is a child of the ByPopulationViewController for the example to work. The text mentions that you don't need to connect the view outlet, but it looks like the other two are still required.--David Parker

The book names the wrong class to use as the File's Owner for the "FileContentsView.xib" nib file in the first paragraph beneath the code on page 145. The sentence in the middle of the paragraph should read as follows: "That's where you'll design the view in IB, and where you'll also connect the outlet and set File's Owner to 'FileContentsViewController'." The book mistakenly used ". . . 'FileOverviewViewController'.--David E. Brown

In the loadFileContentsIntoTextView method the comment on line 6 reads
// read and dump to NSTextView
NSTextView is not available in Cocoa Touch, but UITextView is, so it should read
// read and dump to UITextView--Miranda Janell Ragland

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

Your code for loading settings from the Settings.bundle is erroneous. The settings aren't created until you go to Home/Settings/Your App, so show24Hours is giving you back a result that may not be the default that you asked for. You need to supplement the code to account for this issue. Please do not use a text string to figure it out. While that's convenient for this example, it doesn't work if you don't have a string to look at (for instance, if you are using all toggles.)

I use the latest 3.1.3 iPhone SDK on the latest Snow Leopard version. For me, the generated "Track.h" doesn't have the lines that start with "@interface Track (CoreDataGeneratedAccessors)".--Karsten Silz

There seems to be a memory leak under the "NSFetchedResultsChangeInsert" clause in -(void)controller:didChangeObject:atIndexPath:forChangeType:newIndexPath:

The line

[self.tableView insertSections:[[NSIndexSet alloc] initWithIndex:0] withRowAnimation:UITableViewRowAnimationRight];

should instead read

[self.tableView insertSections:[NSIndexSet indexSetWithIndex:0] withRowAnimation:UITableViewRowAnimationRight];

The corrected version will give back an autoreleased NSIndexSet. The first will leak the alloc'd NSIndexSet.--Ryan McCuaig

The code download dated 2/3/10 contains an error in the code for the Distance Application in the Location directory.

In particular the file named DistanceViewController.h declares the variables lastUpdate, totalDistance, and averageSpeed to be of UILabel type. They should be of UTTextField type.--Wally Wedel