Changes

== Touch controls ==

== Touch controls ==

To navigate through the list of folders and applications you can swipe left and right on the bottom list. To open an item you can tap on it in the list or with it highlighted tap the <code>Open</code> or <code>Launch</code> button prompt in the bottom right. To go back (a folder) you can swipe up or tap the <code>Back</code> button prompt in the bottom right (the latter is only available when no message-box is shown / netloader isn't active). To activate the netloader you can swipe down on the screen. To enter Theme Menu you can swipe left on the screen.

To navigate through the list of folders and applications you can swipe left and right on the bottom list. To open an item you can tap on it in the list or with it highlighted tap the <code>Open</code> or <code>Launch</code> button prompt in the bottom right. To go back (a folder) you can swipe up or tap the <code>Back</code> button prompt in the bottom right (the latter is only available when no message-box is shown / netloader isn't active). To activate the netloader you can swipe down on the screen. To enter Theme Menu you can swipe left on the screen.

= Battery =

= Battery =

The battery/charge status can be displayed, however this is only displayed when the required service is available/accessible.

The battery/charge status can be displayed, however this is only displayed when the required service is available/accessible.

= Netloader =

= Netloader =

With netloader activated as described above you can load apps over the network with nxlink. With the [[Setting_up_Development_Environment|toolchain]] setup run <code>nxlink <nrofile></code> if your network can handle UDP broadcast messages. If nxlink fails with "No response from Switch!" you can use <code>-a <ip address></code> before <code><nrofile></code> for the address to send the app to. See nxlink help for more options.

With netloader activated as described above you can load apps over the network with nxlink. With the [[Setting_up_Development_Environment|toolchain]] setup run <code>nxlink <nrofile></code> if your network can handle UDP broadcast messages. If nxlink fails with "No response from Switch!" you can use <code>-a <ip address></code> before <code><nrofile></code> for the address to send the app to. See nxlink help for more options.

= Themes =

= Themes =

Themes can be optionally loaded from SD "/config/nx-hbmenu/themes/". The theme (or the default) can be selected using the Theme Menu via the - button. This uses [https://hyperrealm.github.io/libconfig/libconfig_manual.html libconfig]. Default settings will be used for any settings not specified in the theme (including themeInfo).

Themes can be optionally loaded from SD "/config/nx-hbmenu/themes/". The theme (or the default) can be selected using the Theme Menu via the - button. This uses [https://hyperrealm.github.io/libconfig/libconfig_manual.html libconfig]. Default settings will be used for any settings not specified in the theme (including themeInfo).

= File Associations =

= File Associations =

File-association cfg files can optionally be loaded from SD "/config/nx-hbmenu/fileassoc/" during startup. There's 1 .cfg file for each app. During normal menu scanning, hbmenu will check for file_extensions/filenames from fileassoc cfg with the dir-list filename, when the file is not recognized otherwise (likewise for directories). This is processed in the same order that the cfg was loaded from SD / same order specified in the cfg file.

File-association cfg files can optionally be loaded from SD "/config/nx-hbmenu/fileassoc/" during startup. There's 1 .cfg file for each app. During normal menu scanning, hbmenu will check for file_extensions/filenames from fileassoc cfg with the dir-list filename, when the file is not recognized otherwise (likewise for directories). This is processed in the same order that the cfg was loaded from SD / same order specified in the cfg file.