Home › jacknutting › Comments
jacknutting
About
- Username
- jacknutting
- Joined
- Visits
- 684
- Last Active
- Roles
- Member, Administrator, Moderator
Comments
-
I guess I'd need to see the whole project to figure it out for certain, but I can try to make some guesses: You say you've got a NameAndColorCell.swift file. Does that file contain the definition of a class called NameAndColorCell? Are you sure ther…
-
Yes, the new book for iOS 8 is out now, and it's become two books - one in Objective-C, and one in Swift. It's also gone back to the *original* title, "Beginning iPhone Development". I hope everyone enjoys it! //jack
-
Glad I could help! //jack
-
Sorry about the late reply. It looks like those files didn't get included for some reason, but you can grab them here: https://dl.dropboxusercontent.com/u/6723123/Tab Bar Icons.zip
-
So, that second image looks really weird. Definitely not what I had in mind, nor what I saw when writing that chapter. Maybe you should download the source archive, verify that it works there, then see if you can spot the difference. The final diffe…
-
Hey, that's really cool! Looks like a useful tool, and I'm glad our book helped get you there!
-
himan83gr, the updated version should have been available several weeks ago, even before you posted! Please log into apress.com again, and check your purchases to see if there's a a new version. I've noticed sometimes on there that they put up a new…
-
We tried to cover this at different points in the book, but but unfortunately configuring constraints in the current version of Xcode is difficult to do properly, and explaining how to do it properly is almost impossible :( However, Xcode 5 seems to…
-
Yeah, you guys are right! Sorry about that. I think that in that section of the applicationDidResignActive: method, since we're not calling a function that returns an error string, we should probably just have something like this inside the for loop…
-
Hmmm. Nothing springs to mind, but maybe you should post the entire .m file, maybe I (or someone else) can spot the problem.
-
Most of the time, if you create a property that is an object pointer, you should either use strong or weak. If it's an IBOutlet to anything other than a top-level object in the nib file, you should typically use weak. However, there are a few classe…
-
You should find it in the menu at the top of the screen, under Product.
-
It's true, clicking the upper-right fullscreen button doesn't really work well with multiple screens, since one of them just turns grey! It looks like Apple is solving this in OS X Mavericks, though: http://www.macrumors.com/2013/06/17/video-shows-d…
-
Do a "clean" (Product > Clean from the menu bar in Xcode), that should force the compiler to rebuild the PCH file the next time it needs it. Hope this helps!
-
Thanks Tym for filling in some great answers! Like Tym says, there are two forms of @synthesize. The first form specifies a single name for both the property (really the getter and setter methods), while the second form specifies one name for the pr…
-
I've also updated the full source archive to contain the fixed version: http://learncocoa.org/9781430245124.zip //jack
-
There are actually instructions on http://learncocoa.org, the section describing the book tells you to navigate to Apress and download from there. Maybe I should make that easier to spot! //jack
-
For your first question, the answer is definitely yes! Just select the view in either your storyboard or nib file, and open the object attributes inspector (opt-cmd4). The uppermost group, "Simulated metrics", contains a "Size" popup where you can p…
-
Strange! The line that you've highlighted in red should look like this instead: NSString *title = [sender titleForState:UIControlStateNormal]; If your Kindle version is showing something else, please verify it for me and I will try to pass the i…
-
For now, you'll find it here: Source Archive //jack
-
Hi Benj, It's really hard to give any general advice without seeing your project. I can guess that "something is wrong in a nib file", but I know that's not very helpful. However I'd be happy to take a look at your project for you. Either upload it …
-
This is almost certainly a conflict between the "classic" iPhone screen size and the new iPhone 5 screen size. You might have your nib file configured for one size, but are running the simulator on a different size. Both of these settings are switch…
-
Oops, that is a serious typo in the book, that was even pointed out by our tech reviewer, but somehow slipped through the cracks anyway! :O This will be the first known item in the errata list for this edition. :( //jack
-
These kind of things can be really frustrating, especially when it's a detail tucked away in a nib file! It's one thing to look at a source code listing and try to spot problems in the code, but quite another to guess about the content of a nib file…
-
As for the errata and discussions: We're just getting started! Except for a few early users, no wider public has known about this forum until the past when when both Beginning iOS 6 Dev and More iOS 6 Dev were published. Welcome aboard, and please p…
-
There's an important distinction between UILabel, which is used just for displaying (not editing) text, and UITextField, which lets the user edit text as well. On the Mac, NSTextField takes both of these roles, but they are separate classes on iOS. …
-
No worries! Xcode nowadays automatically saves all unsaved files as soon as you click "build". In the old days it wasn't so, especially not where nib files were concerned, so the book was written with that in mind. At some point we should perhaps fo…
-
Hi John, Ah, that's one more new trick that the new Xcode has up its sleeve. I'll start a new topic and describe it there. //jack
-
Hi there, Sorry about the late reply, I've been busy as a beaver working on the next edition of the book. Several of the problems you've found are really symptoms of a thing we have to deal with all the time: Apple changes the way Xcode works, or ch…
-
Thanks Mark! That section suffers from a double-fault, as you point out: We missed a bit of explanation, and now the former automated tools are gone. This will all be addressed in the new edition.