Implement a Custom Variable System

[CryZe]

We probably want to have a system that allows storing arbitrary key value pairs (probably both of type string initially). And then allow visualizing them as an info text component. The counter component can then use those to represent its inner state. The Run Editor can show them in the Metadata section. I'm guessing these variables should also have other information such as whether they are transient or are kept across attempts and whether they are read only in the Run Editor. Auto Splitters and components can provide them.

[CryZe]

The categorization so far is:

Scope

• Always: The variable always keeps its value.
• Per Attempt: The variable is only meaningful for a single attempt and resets its value between them.
• Per Split: The variable is only meaningful for a single segment and resets between them.
• Per PB: The variable is represents information about the PB, so it gets reset as the PB changes. (Such as Video URL or Comment)
• Personal: The variable is about the specific runner. When creating route files, these should be reset.
• Category: The variable is about the specific category. When changing the category, these should be reset.
• Game: The variable is about the specific game. When changing the game, these should be reset.

Kind

• User Editable Variable: The variable can be modified, deleted, renamed by the user.
• Automatic Variable: The variable is provided by an auto splitter. The value is only informational. It can't be edited and the value is not stored in splits files.

[CryZe]

Also one really big thing that I didn't even think about until now: We can store all the automatic variables in the segment history. That way you have historic information of so much more than just the split times.