ToggleSwitch - Xenon257R/blue-archive-rainmeter GitHub Wiki

images/toggleoff.png images/toggleon.png

This skin switches on/off skins.

Components & Behaviors

  • luascripts:
    • toggleswitch.lua
  • Is ToggleSwitch; will always at minimum switch itself off
  • Paired with a child Skin toggleon.ini located in the same directory
  • (1000 ms) Update Value: Requires 1-second cycle to check if the user is idle.

Context Menu Options

Name Type Example Notes
skin string BlueArchive\PrimaryBanner Forward slashes (/) will not work.
variant string weatherbanner Do not append .ini or .inc.
main_only boolean true Defines whether or not the skin is only active in the Main Hub.

Mouse Actions

  • Left-Clicking the Tray: Deactivates all the skins catalogued and enabled in the database.

Details

Automatic Timeout

The ToggleSwitch automatically deactivates your catalogued skins if you leave your machine idle for some time. This metric is measured by [x] number of seconds since the last mouse or keyboard input by the Windows OS. By default, the timeout value is 600 seconds (5 minutes) of inactivity. You may set this value to 0 or less as specified by the tooltip to completely disable this feature.

\toggleon.ini

A second skin that comes activated but hidden in the default layout. It does not respond to ToggleSwitch being clicked directly, but hides/unhides itself appropriately according to whether the ToggleSwitch skin is active or not. As such, this skin should never be deactivated, only ever hidden. Otherwise, it will be impossible to re-load the suite unless you have a saved layout, which will also de-activate skins you may have wanted to keep running such as AudioVisualizer or MusicPlayer.

Its attributes are the same as ToggleSwitch except for the following:

  • (1000ms) Update Value: Requires a 1-second cycle to check if ToggleSwitch is active or inactive.
  • Left-Clicking the Tray: Activates all the skins catalogued and enabled in the database.

:speech_balloon: ToggleOn was detached and written as its own skin because this techinque is preferrable over AudioVisualizer's techinque of remembering two locations via variables by having an internal checker that keeps track of every time you move the skin.