Errata
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 |
---|---|---|---|---|---|
Printed | Page xix Using Code Samples section |
Dear Madam / Sir, Note from the Author or Editor: |
Daniel Josiah Akintonde | Jul 15, 2017 | Apr 13, 2018 |
Page 22 Enumeration item 2 and Figure 2-3 |
Step 2, changing the Width of the HorizontalArrangement, should be eliminated (so that the Width remains Automatic) and Figure 2-3 should be updated to show that. These changes are needed so that the the final paragraph on page 22 is correct, namely that the centering can be done at the screen level. The alternative would be to leave Step 2 and Figure 2-3 alone and instead change the final paragraph to say that the horizontal centering should be set in the properties of the HorizontalArrangement itself -- but then Figures 2-4 and 2-5 would need to be updated, so my earlier suggestion seems the simpler approach. Note from the Author or Editor: |
Max Hailperin | Jan 05, 2015 | Apr 13, 2018 | |
Page 34 Figure 2-18 |
The .DrawCircle method of a Canvas object has 4 parameters, not 3: x, y, r and fill. The figure only shows x, y, and r Note from the Author or Editor: |
Anonymous | Sep 20, 2016 | Apr 13, 2018 | |
Printed | Page 39 List Item 4 at bottom of page |
It reads "Also from the User Interface drawer, drag in a Clock component." However, Clock components are located in the Sensors drawer. Note from the Author or Editor: |
andrew petusky | Aug 07, 2015 | Apr 13, 2018 |
Page 61 Figure 4-8 |
I can not see how the join method receives 4 parameters. I only see two, and I can't make it increase to 4. Note from the Author or Editor: |
Anonymous | Sep 20, 2016 | Apr 13, 2018 | |
Page 64 Figure 4-10 |
join does not allow 3 or 4 parameters. It only allows 2. The blocks are not correct in the figure. Also, in figure 4-11 on page 65 Note from the Author or Editor: |
Anonymous | Sep 20, 2016 | Apr 13, 2018 | |
Printed | Page 75-6 Steps 4 and 5 |
Page 75, Steps 4 and 5 have us adding 2 parameters to the DrawEnergyLine procedure. The steps are explicit in that parameter "color" must go beneath the parameter named "length". Note from the Author or Editor: |
Paul Apollo | Jun 22, 2020 | |
Printed | Page 84 Fig 5-19 |
The complete app block diagram in Fig 5-19 on page 84 has an error in the Restart-button block. It wrongly sets Ladybug.visible to true, but should set Ladybug.enabled to true, as is shown in Fig 5-15 on page 80. Note from the Author or Editor: |
Jeff Johnson | Mar 08, 2017 | Apr 13, 2018 |
Printed | Page 101 table 7-1 |
On page 101, chapter 7, The table. 7-1 misnamed some components. Note from the Author or Editor: |
Anonymous | Nov 04, 2015 | Apr 13, 2018 |
Printed | Page 132 Last row of Table 9-1 |
Clock is listed as being in the User Interface component group. It is actually in the Sensors group. Note from the Author or Editor: |
Jeff Johnson | Mar 08, 2017 | Apr 13, 2018 |
Printed | Page 137 top |
The sound files 6.wav and 7.wav are in reverse order. To have the xylophone play a correct scale, you must switch them. Note from the Author or Editor: |
Jeff Johnson | Mar 08, 2017 | |
Printed | Page 145 Fig 9-15 |
The PlayButton.click block shown in Fig 9-15 on page 145 of the book is missing a call to PlaybackNote. Without that, the app won't start playing back the recorded notes. Fig 9-13 on page 142 shows the correct code for PlayButton.click. Also, the section on page 141-142 that contains Fig 9-13 is misleading: it says it is a "thought experiment" and "we could (but won't)" do what is illustrated. Many students discount everything in the figure, when what is meant is that the *recursion* is a thought experiment that won't be in the actual solution. The PlayButton.click block IS part of the actual solution. Note from the Author or Editor: |
Jeff Johnson | Mar 08, 2017 | Apr 13, 2018 |
Printed | Page 145 Variation 1 |
The first Xylophone variation has an error in the last sentence: "To re-enable it (the Reset button) when the song is complete, change the IF THEN block in PlayButton.Click into an IF ELSE block, and re-enable Reset button in the ELSE portion." That won't work. Yes, disable the ResetButton in PlayButton.click. But don't re-enable it there; the tune won't be finished. Re-enable the ResetButton when the song is finished playing: at the IF THEN block in PlayBackNote. The IF tests if there are more notes to play. The code in the THEN section is what executes when there are more notes to play. If you change the IF THEN to an IF THEN ELSE block, the ELSE section is where you put code that is to be executed when there are NOT more notes to play. So you should enable the Reset button in the ELSE portion. Note from the Author or Editor: |
Jeff Johnson | Mar 08, 2017 | Apr 13, 2018 |
Printed | Page 145 last line |
Space needed in "ifelse" so it is "if else". |
Jeff Johnson | Mar 08, 2017 | Apr 13, 2018 |
Printed | Page 200 Last sentence |
The link aiamazonapi.appspot.com/ does not exist. Note from the Author or Editor: |
Tan Kah Sin | Mar 14, 2016 | Apr 13, 2018 |
Printed | Page 323 bottom of 323 and top of 324 |
We need to remove an example in ch. 24 which refers to a Yahoo Finance API. |
David Wolber |
Mar 14, 2018 | Apr 13, 2018 |
PDF, ePub, Mobi | Page 12620 text |
Typos: Note from the Author or Editor: |
Anonymous | Sep 17, 2019 |