Programming iOS 8

Errata for Programming iOS 8

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
ePub
Page 1
header, titlepage

I downloaded the ebook on kindle / iPad. The title is "Programming iOS 7" instead of "Programming iOS 8". This is found systematically in the page headers, the page 2 of the book and the Content / directory.

Dr. Ralf Kaiser  Sep 17, 2014  Nov 21, 2014
ePub
Page 2?
Title

Title of book and title page (after the image page in the epub) has "Programming iOS7"

James Troi  Sep 17, 2014  Nov 21, 2014
PDF
Page 8
2nd paragraph

"simple solution is add a line of code" I think it should be "is to add"

Anonymous  Oct 17, 2014  Nov 21, 2014
Printed
Page 10
next to last paragraph

If you need a reference to a particular view, you will probably arrange this beforehand as property, perhaps through an outlet. should be ...as a property, perhaps...

Note from the Author or Editor:
fixed in my copy

Gary Meyers  Feb 24, 2015  May 01, 2015
ePub
Page 30
2d paragraph under Transform

Didn't you mean to write "...so there's *no* need to represent them in the struct)"?

Note from the Author or Editor:
Good catch, thanks! Fixed in my copy.

Ronnie Pitman  Jan 06, 2015  May 01, 2015
PDF
Page 45
top paragraph

"changes to your constrants over time" I think it should be "constraints"

Note from the Author or Editor:
Thanks, fixed in my copy.

Anonymous  Oct 17, 2014  Nov 21, 2014
PDF, ePub
Page 65
Third paragraph

3rd paragraph beginning of chapter two, it says: "For how to draw text, see Chapter 12". I think what is meant is: "For how to draw text, see Chapter 10". (I.e. switch 12 to 10 and adjust the link) Why? Because chapter 12 is about a lot of interesting controls, but none seemingly specific to text, whereas chapter 10 is called "Text" and begins by discussing drawing text.

Note from the Author or Editor:
I completely agree!

Egghead Games  Jun 19, 2015 
Printed
Page 162
next to last paragraph

A important use of transactions is to turn implicit animation off. should be An important...

Note from the Author or Editor:
Corrected in my copy.

Gary Meyers  Feb 24, 2015  May 01, 2015
Printed
Page 269
fourth paragraph

I think The root view, and any other fullscreen view, must occupy the entire window, including the status bar area, the top 20 pixels of the view being visible behind the transparent status bar. should be ...the top 20 points...

Note from the Author or Editor:
Deleted "20 pixels" in my copy.

Gary Meyers  Feb 24, 2015  May 01, 2015
Printed
Page 280
second paragraph

If we were to do the same thing without using autolayout, viewDidLoad would be unwise choice;... should be ...would be an unwise...

Note from the Author or Editor:
Added "an" in my copy.

Gary Meyers  Feb 24, 2015  May 01, 2015
Printed
Page 320
next to last paragraph

As the gesture begins, we create the UIPercentDrivenInteractiveTransition object and store it in an property (self.inter). should be ...in a property...

Note from the Author or Editor:
corrected in my copy

Gary Meyers  Feb 25, 2015  May 01, 2015
Printed
Page 343
fourth paragraph

For example, by lying to a split view controller ... even on an iPad. should be ... even on an iPhone.

Note from the Author or Editor:
Good catch. Fixed in my copy.

Gary Meyers  Feb 26, 2015  May 01, 2015
Printed
Page 396
second paragraph

The word "the" is duplicated in But that means that the the scroll view underlaps the status bar.

Note from the Author or Editor:
fixed in my copy

Gary Meyers  Feb 28, 2015  May 01, 2015
Printed
Page 442
first paragraph

The row data somehow be clumped... should be The row data must somehow be clumped...

Note from the Author or Editor:
corrected in my copy

Gary Meyers  Mar 01, 2015  May 01, 2015
PDF, ePub
Page 501
1st paragraph

Under the heading "Preparing a Popover", the first sentence needs a "to" inserted, i.e. you’re going present a view controller , vs you’re going to present a view controller

Egghead Games  Jun 20, 2015 
PDF
Page 865
Person class code

It is not necessary to use @NSCopying and NSString (although it works), i.e. class Person: NSObject, NSCoding { var firstName: String var lastName: String ... is also correct (and easier to understand at first sight). However, one could emphasize that Person has to inherit from NSObject to prevent a runtime error (unfortunately, no compile-time error occurs when Person has no parent). Thanks for a great book!

Note from the Author or Editor:
Agreed, and I've taken out the NSCopying from the book and from the online examples. I can only guess that during very early phases, when I was first translating the example from Objective-C to Swift, this had to be an NSString and therefore as a matter of policy I used NSCopying to go with it.

Alexander Niske  Dec 02, 2014  May 01, 2015