Historical errata for Rapid Android Development

Working off established UI standards, we can build apps that are more intuitively to use, and enable to user to get the job done quickly while on the move.

Gravity (software-based) Calculates the orientation of the device, returning
a tree dimensional vector indicating the direction and magnitude of
gravity

Sure, the UI might not adapt as needly if we set num to 100, for example.

Now that we have an array in which to store our colors, let’s talk about its sidekick: the forloop.

You may want to discuss the need for a USB driver for adb to use USB debugging (See developer.android.com/tools/extras/oem-usb.html for installation instructions). It was not installed automatically for either of my two devices.

The Processing language and also provide APIs we can use
to analyze, at the pixel level, the content of the images that we capture.

In the building the game,

Appendix 1, A1.1

Jelly Bean (5.0)

Chapter 3.5 “Run the app”

Wrong shortcut in “Remember the shortcut for Run on Device is SHIFT CMD R”. Should be CMD R without shift.

This is a general suggestion pertaining to all ebooks. Is it possible to make the ‘report erratum’ link on each page of the pdf automatically fill the page number field on the web form?

Only Hardware acceleration makes is possible to animate
thousands of data points

The method define the window
width and height

Sets Sets the default values for ambient light

where we translate the our finger position

into a light direction of the
directional light.

This time, we don’t need to set Android
permissions or import any libraries since this we are not using hardware that
requires authorization

Create the SPHEREPShape object we’ll use to render the Earth, at a size of
height/3

Change to:

Create the SPHEREPShape object we’ll use to render the Earth, with a size of one third the device screen height

When we use images as textures for 3D object in Processing

Now let’s Let’s take only at the parts of the code that deal with the 3D box, and camera texture.

Now that we’ve learned how to work with static and moving image textures, let’s now take a closer look at the different types of light sources we can work with in Processing.

I feel that the second now is superfluous, I’ve noticed it in a couple of other places too.

and we set increase it to 60 vertices
for per revolution

We can set the lihgt color

The pointLight()20 method takes only the light color
and position a parameters.

They are already present in the on page 300, but currently commented out.

Using Processing’s createFont()21 method, we can load an already installed system font load it into our app at a defined font size.

which allows us import any font we’d like

Both methods require that we set the current font to draw text() in our sketch to the font we’ve created or loaded, using the textFont()23 method.

Insert used? ‘current font used to draw’

Calculate the distance between the finger tip ant the text position on the screen

Move your finger across the touch screen surface, and observe how the text closes to the finger tip enlarge

and make the text we’ll diplay scalable

Processing has just created a custom Droid Serif font for us to use in our sketch, compiling Processing font file called DroidSerif-48.vlw into our sketch’s
data folder.

After all, we’ve created the Droid Serif font at 48 points, and because each glyph is rendered as a bitmap images

the same rule applies like for any other pixel image

the same rule applies as for any other pixel image

becoming bigger as you move down your finger and smaller as you move up.

becoming bigger as you move your finger down and smaller as you move up.

or

becoming bigger as you move your finger down the screen and smaller as you move up.

Last sentance on the page is “The apps we create can be shard”
Should be changed to “The apps we create can be shared”

I think that the explanation about the method orientation() should not be in the paragraph “Using colors”.

motionPressure() doesn’t work as described, it returns always the same value when running the code examples in the book at page 51 or 43.
I don’t know if it is an hardaware problem (samsung galaxy S GT I900) or if this method has been dropped,
wiki.processing.org/index.php?title=Android&redirect=no#Mouse.2C_Motion.2C_Keys.2C_and_Input

motionPressure not working since 2.0b7 as you already probably know

We us it to navigate

The fill line should be:
fill(dist(pmouseX, pmouseY, mouseX, mouseY), 1, 1);

Section 3.8, paragraph 2. The text in the PDF version reads “To implement the color picker, let’s rework our code, on page 49,”, but in the Kindle version it’s missing the link text “code, on page 49,”. This also occurs in other links (eg on p56 “Add the code snippet below to the code, on page 49,” is missing the text “code, on page 49”).

The two notes starting “Release the camera…” (which would be numbered 7 and 8) are missing their targets in the code.

I cannot put html in the description, because your form refuses! I’ve tried my best…

footnote 5, second URL is incorrect: “Manindra29/XQMode/XQMode%20v0.4a.zip”

It should be: https://_github.com/Manindra29/XQMode

order of fields in fill(1, 1, dist(pmouseX, pmouseY, mouseX, mouseY)); is wrong, should be: fill( dist(pmouseX, pmouseY, mouseX, mouseY), 1, 1);

I love every bit of this book! Here’s a quick eerro

First, the Gyro code snippet is incorrect. It should read:

void onGyroscopeEvent(float x, float y, float z)
{
rotation.x = x;
rotation.y = y;
rotation.z = z;
}

and if the Gyro code snippet is to work then you must also add:

At the global varialbles:
…
PVector rotation;

And in setup(){
…
rotation = new PVector();

And in draw(){ after the Magnetic field stuff:
+ “Gyro :” + “\
”
+ “x: ” + nfp(rotation.x, 1, 2) + “\
”
+ “y: ” + nfp(rotation.y, 1, 2) + “\
”
+ “z: ” + nfp(rotation.z, 1, 2) + “\
”

And you must correct the error in the code snippet:
void onGyroscopeEvent(float x, float y, float z)
{
rotation.x = x;
rotation.y = y;
rotation.z = z;
}

Cheers!

another error: snippet should be:

void onGyroscopeEvent(float x, float y, float z)
{
rotation.set(x,y,z);
}

then, later on page 55 the PVector variables are incorrectly called accelerometerX, accelerometerY, and accelerometerZ instead of accelerometer.x etc.

Here, you use individual variables instead of PVector which was carefully explained a fex pages earlier. This is inconsistent and could be confusing for a non-expert programmer.

The last element of an array is not correctly indicated:

“and the last element, palette.length.”

It should read “palette.length-1” or you will get an error.

The code for the example ScalableVectorGraphics is missing this import line (in the code download):

import android.view.MotionEvent;

Same omission as page 311: in the code download as well..

import android.view.MotionEvent;

same error as p 311,314, missing import in code, also missing in the code download: ObjectFiles.pde

import android.view.MotionEvent;

mobius.pde:
will not run on my Nexus 4, error message is
“Smooth is not supported by this hardware (or driver)”
Just causes screen to flash black and exit..

The PShape method .end no longer exists it is replaced by endShape. The downloaded code fails to compile as a result.

Also, like the other Moebius, this code crashes on my Nexus 4, with the error about smooth not being supported.

This whol section about PShapes is very disappointing, I am sorry to have to say…

the use of Table(this, “groceries.txt”); //(1)

fails at compilation…

cannot find symbol
[javac] symbol : constructor Table(processing.test.datareadgroceries.DataReadGroceries,java.lang.String)
[javac] location: class processing.data.Table
[javac] groceries = new Table(this, “groceries.txt”); //(1)
[javac] ^

This means that all the section on Tables is wrong…

The part of the osc5 message declaration is inside the onAccelerometerEvent method. Gives an error. The message construction should be inside the draw part.

Setting the longitude is shown as a comment. It is also a comment when you download the code Geolocation.pde

double _altitude, float _accuracy) { //(5) longitude = _longitude;

instead of
…
try{
earthquakes = new Table(this, src);
…
use:
…
try {
earthquakes = loadTable(src); //(2)
…

5 - Count …in colors
change to:
5- Count … in columns

Here are the steps we need to take.
…
2 - Import android.content.Intent class because we need onActivityResult(), which is called when the apps starts up immediately before onResume() in the activity cycle. See void onActivityResult(in requestCode, int resultCode, Intent data) method on EnableBluetooh.pde.

Instead of:
3.Select the Ketai library…
Use:
3.Select the oscP5 library…
That´s it!

Note 18 is a copy+paste of note 17 explaining onPinch instead of explaining onRotate.

I typed in the code bit by bit and ran the code with first only setup(), draw() and onTap() methods. Could not see anything happening.
So I went on with onDoubleTap() but still nothing. Turned out I needed the surfaceTouchEvent() for it to work, which was obvious once I started to look for problems.
Once I figured this out I could safely refactor a bit to reduce the printing code duplication by implementing my own printEvent() method.

Maybe you should move surfaceTouchEvent() to be the first method after draw() to make the app by default “work” for any number of “onXxx” methods implemented? That way us learners can have an even more incremental approach and fewer speed bumps.

The code in ColorPickerComplete changes the variable names r, g and b (which makes some sense although a bit short for my taste) to ch1, ch2 and ch3 (which makes no obvious sense to me, ch = channel?).
Since the code builds on the previous example I think it should be consistent with it.

The code in ColorPickerComplete changes the variable names r, g and b (which makes some sense although a bit short for my taste) to ch1, ch2 and ch3 (which makes no obvious sense to me, ch = channel?).
Since the code builds on the previous example I think it should be consistent with it.

Speed bump! The section about permissions need to come before the code or the code will fail to run when entered. When I’m done with my code I want to run it immediately. I do not want to read two more pages first.

Bug: In method onLocationEvent(…) the longitude assignment is commented out.

There is an error in the code written in the book for DataReadGroceries.pde as the code does not match the downloaded code.

One the first line in the function setup the code reads:

groceries = new Table(this, groceries.txt");

but the downloaded code for DataReadGroceries is:

groceries = loadTable(“groceries.tsv”);

There is an error in the code written in the book for DataRead.pde as the code does not match the downloaded code.

One the first line in the function setup the code reads:

colors = new Table(this, “colors.csv”);

but the downloaded code for DataRead.pde is:

colors = loadTable(“colors.csv”);

The sentence that straddles pp 79-80 is “We then convert…into miles by multiplying distance by…” implying that the program that follows will convert the distance from meters to miles. However, the program (LocationDistance.pde) does not make this conversion — distance is displayed in meters.

The type android.location.Location cannot be resolved. It is indirectly referenced from required .class files.
This error occurs (first) at: float bearing = location.getLocation().bearingTo(otherDevice);
Do not have a clue how to resolve it.

The last 2 lines of the program are

targetX = int(random(25, width - 35));
targetY = int(random(25, width - 35));

I would have expected the ranges to be symmetric. So either the 25’s should be 35 or the 35’s should be 25.

On p 159 the OscMessage m is created with an addrPattern of “/remoteMouse/” in function mouseDragged(). However, on p 160, when the message is received as a KetaiOSCMessage, the addrPattern is checked for as “/remoteCursor/” (in function onBluetoothDataEvent()) so no communication actually occurs. Making these strings the same fixes the issue.

This is while running the app DataWriteExternal. The created file can be seen in the device, but when the device is connected to PC, it is not visible in the PC. It turns out that this error is due to a long-standing google bug, see code.google.com/p/android/issues/detail?id=38282 (hyperlinks are not allowed here, so I just deleted the header part of this link). The simplest solution to this problem is to boot the device, a workaround is to run a background app (suggested in the above link) which refreshes the MTP periodically. A permanent solution is not yet available from google.

This is the code for app Data/DataEarthQuakes. The .txt extension for the file is not accepted by the code, gives this error: “No extension specified for this table”. It works if you change the extension to .csv.

Secondly, the error for DataWriteExternal also occurs for this app in a different way. After running the app successfully once, if you change the name of the internet file and run the app again, the app still thinks it has got the old file-name and then gives some arbitrary error citing some bad data. Again, a device reboot solves this problem. This is with android 4.4.2 and the latest software downloaded.

Last line says “port 1200”; should be "port 12000)

2.0 download does not have the Android or Javascript modes pre installed and there are no directions on where to find the necessary files.

“Besides the default Java mode, the drop-down menu in Processing
2.0b8 is already preloaded with the Android and JavaScript mode. In the
final release of Processing 2.0, this drop-down will be slightly different. You’ll
need to add the Android mode, choosing “Add mode…”