Pre-release for Pak authors. It supports both Anbernic H700 and TrimUI devices, and it's otherwise the same as rc10.

What's changed

The only change since rc10: on H700 devices, apps that use SDL now see the built-in buttons with the same numbers as on TrimUI devices, on every H700 model.

• Before, the numbers depended on the model. On the RG SP, for example, A was button 3 and B was button 4.
• Now every H700 model uses the TrimUI numbers: B = 0, A = 1, Y = 2, X = 3, L1 = 4, R1 = 5, SELECT = 6, START = 7, MENU = 8, L3 = 9, R3 = 10. L2 and R2 are triggers (axes 2 and 5), the sticks are axes 0/1 and 3/4, and the D-pad is hat 0.
• SDL also recognises the built-in controls as a standard controller, so apps that use SDL's controller support get working buttons without a mapping of their own.
• The Files app now uses these numbers.

NextUI itself, its other tools and all MinArch emulators read the buttons directly and are not affected.

Paks need updating

Paks that read the H700 buttons through SDL and have the old numbers built in will get the wrong buttons until they're updated. These include:

• Pak Store, and other Paks built on the gabagool library
• Nintendo DS (DraStic and DSperate)
• ScummVM Standalone
• Itch.io Store
• PICO-8 (A and B are swapped)

The fix is usually small: on H700, use the same button numbers or controller mapping as on TrimUI (tg5040). Porting NextUI Paks to H700 has the details.

Until a Pak is updated, adding this line to its launch.sh brings back the old numbers for that Pak only:

export SDL_JOYSTICK_H700_FIXED_LAYOUT=0

Known issues

• Pak Store buttons are mixed up until the Pak Store is updated: A is on X and B is on L1. The line above fixes it for now.
• Updater has scaling issues and can freeze up your device. Do not start it.
• LedControl pak may not display text properly on light coloured themes.

How to install or update?

See the wiki page for details.