Notes - Xenon257R/blue-archive-rainmeter GitHub Wiki

images/notes.png

This skin is a notes section where you can write down various information for quick reference.

Components & Behaviors

  • (0/-2) AlwaysOnTop Value: When hovered over, will change to be Normal (0) so that it renders atop all other skins, before returning to the desktop (-2) when the cursor leaves.

Mouse Actions

  • Double Left-Clicking the Clipboard: Opens the currently selected .txt file.
  • Hovering Over the Clipboard: Reveals the contents of the .txt file, unless marked sensitive.
  • Right-Clicking the Clipboard: Navigates to the next .txt file in the queue, if any.
  • Scroll-wheeling over the Pop-Up: Scrolls up and down the contents of the .txt file.
  • Left-Clicking the arrows to the right of the Pop-Up: Scrolls up and down the contents of the .txt file, respectively.

Context Menu Options

Name Type Example Notes
file_id number 12345 - and . will be accepted by the input, but ignored by the script, i.e. -1.23 is the same as 123.
sensitive boolean true

Details

:speech_balloon: Security is Only 2 Mouseclicks Worth

Absolutely under no circumstances should you think about putting sensitive information in .txt files, such as Bank Account Details or passwords. While there exists a sensitive option, the most it does is prevent accidents where you accidentally hover of the skin and reveal its contents immediately. There are better ways to go about safely and securely storing said information such as password managers, and this skin is best treated as a digital sticky-note.

Breaking Down file_id

file_id is a number that generates an associated .txt file of the same ID (after stripping - and . occurrences). As such, multiple entries sharing the same file ID will cause both of those entries to point to the same file, meaning when you change the contents of the file, it will effect both entries. This is particularly important when a sensitive entry shares the same ID as a non-sensitive one, so be careful!

This system opted to use a numeric system because while it would have been easier to just use the name parameter to generate the .txt file, it cannot be ruled out the disaster certain characters such as \ or : may bring, which name is perfectly fine accepting.

:speech_balloon: Yes, I could've used a hash table, but that got hairy real fast and I got stuck for a long time trying to untangle the mess, so I threw in the towel with that implementation. For now. Might be a bit hard to revisit considering backwards compatibility and all.