Changes

Jump to navigation Jump to search
574 bytes added ,  01:22, 9 August 2019
no edit summary
Line 6: Line 6:  
= Controls =
 
= Controls =
 
Use the D-Pad/joystick to select the app/directory, up/down can be used for faster scrolling. Press A to launch the app. Navigating directories is supported, press A to enter a directory and press B to leave the current directory. Press Y to activate netloader and press B to deactivate netloader.
 
Use the D-Pad/joystick to select the app/directory, up/down can be used for faster scrolling. Press A to launch the app. Navigating directories is supported, press A to enter a directory and press B to leave the current directory. Press Y to activate netloader and press B to deactivate netloader.
 +
 +
Press the - button to enter Theme Menu. Press X to (un)star the current menu entry.
    
== 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 =
+
To (un)star the current menu entry you can touch the (un)star button prompt.
 +
 
 +
= Status =
 
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.
 +
 +
The local-time and network status are also displayed.
    
= Netloader =
 
= Netloader =
Line 19: Line 25:  
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).
   −
The string used for displaying the buttons can be set with buttonAText, buttonBText, and buttonMText, but normally this can be left at the defaults. Change the value of the enableWaveBlending field to 1 to enable wave blending.
+
See [[Homebrew Themes]] for a list of themes.
 +
 
 +
The string used for displaying the buttons/stars can be set with buttonAText, buttonBText, buttonXText, buttonMText, labelStarOnText, and labelStarOffText, but normally these can be left at the defaults. Change the value of the enableWaveBlending field to 1 to enable wave blending.
    
There's also borderColor, borderTextColor, and progressBarColor fields which can be set like the other color fields.
 
There's also borderColor, borderTextColor, and progressBarColor fields which can be set like the other color fields.
Line 60: Line 68:  
When processing directories where no NRO was detected, hbmenu will go through the dir-listing and use the first entry where the filename matches a fileassoc entry where <code>filename</code> is specified (file_extension entries are skipped).
 
When processing directories where no NRO was detected, hbmenu will go through the dir-listing and use the first entry where the filename matches a fileassoc entry where <code>filename</code> is specified (file_extension entries are skipped).
   −
The generated menu entry launches the specified app_path where the first passed argument (argv[1] in the launched app) is the absolute filepath for the associated file. See below regarding the icon used for the menu entry. The author and version fields for the menu entry are loaded from app_path, while the name is the filename (unless a directory is being processed, in this case the directory name is used).
+
The generated menu entry launches the specified app_path where the first passed argument (argv[1] in the launched app) is the absolute filepath for the associated file. See below regarding the icon used for the menu entry. The author and version fields for the menu entry are loaded from app_path, while the name is the filename (unless a directory is being processed, in this case the directory name is used). Git-only: when {$FILEPATH with extension changed to .nacp} exists, the aforementioned strings will be loaded from there instead.
    
The only optional setting is icon_path. All paths are absolute. Icon will attempted to be loaded from the following: {$FILEPATH with extension changed to .jpg} -> icon_path setting if it exists (target setting -> main file_assoc setting) -> icon from app_path.
 
The only optional setting is icon_path. All paths are absolute. Icon will attempted to be loaded from the following: {$FILEPATH with extension changed to .jpg} -> icon_path setting if it exists (target setting -> main file_assoc setting) -> icon from app_path.
 +
 +
If {$FILEPATH with extension changed to .nacp} exists the nacp is loaded from there, otherwise the fileassoc config is used.
    
If you have targets where file_extension and filename both have the same extension, the filename target should be located before that file_extension target in the cfg. Targets which have both file_extension and filename settings are ignored. Each target must have either a file_extension or filename setting.
 
If you have targets where file_extension and filename both have the same extension, the filename target should be located before that file_extension target in the cfg. Targets which have both file_extension and filename settings are ignored. Each target must have either a file_extension or filename setting.

Navigation menu