Index Chapter 19

marijnh · marijnh · commit 77e046b71f62 · 2018-01-22T17:02:17.000+01:00
diff --git a/03_functions.md b/03_functions.md
@@ -1062,7 +1062,7 @@ hint}}
 
 ### Bean counting
 
-{{index "bean counting (exercise)", [string, indexing], "zero-based counting"}}
+{{index "bean counting (exercise)", [string, indexing], "zero-based counting", ["length property", "for string"]}}
 
 You can get the Nth character, or letter, from a string by writing
 `"string"[N]`. The returned value will be a string containing only one
diff --git a/04_data.md b/04_data.md
@@ -1140,7 +1140,7 @@ equal to zero and below 10. Since `Math.floor` rounds down, this
 expression will produce, with equal chance, any number from 0 through
 9.
 
-{{index "Math.ceil function", "Math.round function"}}
+{{index "Math.ceil function", "Math.round function", "Math.abs function", "absolute value"}}
 
 There are also the functions `Math.ceil` (for "ceiling", which rounds
 up to a whole number), `Math.round` (to the nearest whole number), and
diff --git a/07_robot.md b/07_robot.md
@@ -104,8 +104,8 @@ If you're thinking in terms of ((object-oriented programming)), your
 first impulse is probably to start defining objects for the various
 elements in the world. A ((class)) for the robot, one for a parcel,
 maybe one for places. These could then hold properties that describe
-their current state, such as the pile of parcels at a location, which
-we could change when updating the world.
+their current ((state)), such as the pile of parcels at a location,
+which we could change when updating the world.
 
 This is wrong.
 
@@ -127,9 +127,9 @@ entire jungle.
 
 quote}}
 
-Instead, let's condense the village's state down to the minimal set of
-values that define it. There's the robot's current location and the
-collection of undelivered parcels, each of which has a current
+Instead, let's condense the village's ((state)) down to the minimal
+set of values that define it. There's the robot's current location and
+the collection of undelivered parcels, each of which has a current
 location and a destination address. That's it.
 
 {{index "VillageState class", "persistent data structure"}}
diff --git a/15_event.md b/15_event.md
@@ -21,7 +21,7 @@ react to it as it occurs.
 {{index polling, button, "real-time"}}
 
 Imagine an interface where the only way to find out whether a key on
-the keyboard is being pressed is to read the current state of that
+the ((keyboard)) is being pressed is to read the current state of that
 key. To be able to react to keypresses, you would have to constantly
 read the key's state so that you'd catch it before it's released
 again. It would be dangerous to perform other time-intensive
@@ -187,7 +187,7 @@ the event. This can be useful when, for example, you have a button
 inside another clickable element and you don't want clicks on the
 button to activate the outer element's click behavior.
 
-{{index "mousedown event"}}
+{{index "mousedown event", "pointer event"}}
 
 The following example registers `"mousedown"` handlers on both a
 button and the paragraph around it. When clicked with the right mouse
diff --git a/16_game.md b/16_game.md
@@ -218,7 +218,7 @@ in the exercises of [Chapter ?](object#exercise_vector).
 
 As the game runs, actors will end up in different places or even
 disappear entirely (as coins do when collected). We'll use a `State`
-class to track the state of a running game.
+class to track the ((state)) of a running game.
 
 ```{includeCode: true}
 class State {
@@ -635,7 +635,7 @@ defined earlier.
 .player { background: rgb(64, 64, 64);   }
 ```
 
-{{index graphics, optimization, efficiency}}
+{{index graphics, optimization, efficiency, state}}
 
 When it updates the display, the `drawState` method first removes the
 old actor graphics, if any, and then redraws them in their new
diff --git a/18_http.md b/18_http.md
@@ -1006,7 +1006,7 @@ Objects in the `files` object have properties such as `name` (the
 filename), `size` (the file's size in bytes), and `type` (the media
 type of the file, such as `text/plain` or `image/jpeg`).
 
-{{index "asynchronous programming", "file reading", "FileReader type"}}
+{{index "asynchronous programming", "file reading", "FileReader class"}}
 
 {{id filereader}}
 
@@ -1032,14 +1032,14 @@ avoid freezing the document.
 </script>
 ```
 
-{{index "FileReader type", "load event", "readAsText method", "result property"}}
+{{index "FileReader class", "load event", "readAsText method", "result property"}}
 
 Reading a file is done by creating a `FileReader` object, registering
 a `"load"` event handler for it, and calling its `readAsText` method,
 giving it the file we want to read. Once loading finishes, the
 reader's `result` property contains the file's content.
 
-{{index "error event", "FileReader type", "Promise class"}}
+{{index "error event", "FileReader class", "Promise class"}}
 
 _FileReader_s also fire an `"error"` event when reading the file fails
 for any reason. The error object itself will end up in the reader's
diff --git a/19_paint.md b/19_paint.md
diff --git a/code/solutions/19_1_keyboard_bindings.html b/code/solutions/19_1_keyboard_bindings.html
