What's new in v0.8.0-beta.2

A follow-up to beta.1, and only about interface haptics. Game rumble, shaders and
everything else are unchanged.

Rumble worked in games in beta.1, but whole screens in the interface stayed
silent. That was not a list of oversights so much as one design fault: the code
that decided "the cursor moved, tap" was written separately for each screen, so
a screen only responded if someone had remembered to teach it. Silence was the
default. This build moves that decision underneath, into the shared list and
keyboard code, so a screen responds because of what it is rather than because it
was remembered.

Screens that now respond

The System menu tab row. Up and down in Actions and Info. The Pak Rat list and
its detail page. Every 5-Game Mode setup screen: picking games, arranging them,
the lock and style choices, and the PIN entry. The app switcher. Search results.
The Apps browser. The Tools overlay. Jumping by letter in Cover Flow.

Backing out feels like going in

Opening a screen tapped; closing it mostly did not. Leaving Search, the
switcher, the Apps browser, the game browser, Pak Rat or a settings page now
taps the same way entering it does.

The keyboard

Both keyboards tap as you move between keys and as you type, and buzz at the
edges: backspace on an empty field, or pushing the text cursor past either end.

This follows your movement setting, so the keyboard stays quiet unless you have
turned that on.

A renamed setting

Settings > Controls & Feedback > Navigation Tick is now Cursor Movement.

Same setting, honest name. It only ever controlled the tap when the cursor
moves, but "navigation" read like it covered moving around the interface
generally, so people expected it to silence everything. Opening a screen and
confirming an action still tap with it off. To silence everything, use the
Rumble master switch.

Smaller fixes

• Home Layout, Color Scheme and Bluetooth changed without any feedback, unlike
  every other setting on those pages.
• Scrolling to the bottom of Device, Library or Playtime reported movement that
  had not happened.
• Opening the in-game menu and closing it again were both silent.
• Selecting a game in 5-Game Mode, clearing the list, and Rescan Library now
  report what happened, including refusing a sixth game.

Testing notes

The useful thing to hunt for is two taps from one press. Almost everything
here routes through shared code now, so if something double-taps it will most
likely be a screen that kept its old hand-written tap as well. The tab row,
channel switching in Cover Flow, and opening or closing the system menu are the
likeliest candidates.

Also worth a pass with Cursor Movement off: movement should go quiet
everywhere including typing, while boundaries, confirmations and screen changes
keep working.