List - Xenon257R/blue-archive-rainmeter GitHub Wiki

The List skin variants are the central component of Sub Hubs and refer to a secondary suite layout that can either be loaded directly using an .rmskin packaged layout, or by programming in a line of code into a MouseAction that when activated, will switch to the Sub Hub from (presumably) the main hub.

All Lists have slightly different predefined Components and Behaviors as listed below:

Components & Behaviors

  • @includes:
    • config.inc
  • (-1) Update Value: Only updates once on startup with a few behavioral exceptions
  • (-2) AlwaysOnTop Value: Will stick to the desktop and never render over other applications
  • (1) KeepOnScreen Value: Will be constrained within the bounds of the desktop
  • (%100, 0) Anchor Point
  • Not Draggable
  • Cannot Exist With ToggleSwitch
  • Influences the Tray Size

To test it in action, the default installation programs all SchaleFolder variants to load up the AronaGrid with a Right-Click. In the resulting sub hub, you can click on the HomeButton to return to the Main Hub. You can change the List variant you wish to go to as well as apply further augmentations using Context Menu options.

Currently, only TrayApps and SchaleFolder can use the codes to switch hubs. The codes are as shown below:

Code Function
#LSCR# Emulates a transition screen.
#GRID# Switches to the Arona System Grid layout
#SHOP# Switches to the Sora Shop layout
#DNGN# Switches to the Momoka Search Engine layout
#RAID# Switches to the Rin Game Catalog layout
#QSTS# Switches to the Ayumu Quests layout

To use the code, simply write it into the appropriate field. In a TrayApp, this is the Execution parameter. For SchaleFolder, select the Context Menu option labeled Edit Right-Click and write in the code in the pop up that shows. So for example, if you wish a TrayApp to switch to the Arona Grid layout with the transition screen, the code you would write in is #LSCR##GRID#.

As a general rule of thumb, every code implementation should optionally start with #LSCR# depending on if you want the transition animation, followed up by 1 of the 5 remaining codes. Writing any further than that may yield unexpected results, or straight up crash Rainmeter to the point of no recovery.

Implementing Hub Switching in other Skins

If you're willing to configure .ini files beyond GUIs, it is really easy to apply this feature to any skin you wish. Under the [Variables] section of the skin, simply include the @Resources\template\hubswitch.inc config file, and now all the codes will function when used as variables - just write them into a parameter such as LeftMouseUpAction, and it will work as seamlessly as it did for the preprogrammed skins.

The Home Button

As these are secondary hubs, a HomeButton skin comes equipped for returning to the Main Hub. If not desired, you can simply turn off the skin.