Once I verified void 'KillRunningScripts();' was BROKE, I kinda put this all on hold.
Just so there won't be a whole lot of new surprises, there ALSO seems to be some hints,
that scripts may going from the old "C-like", to Python.
First there are TWO repositories for scripts, each with their OWN [Win7] naming convention:
- C:\Program Files (x86)\SoundSpectrum\G-Force\Scripts
- C:\Users\YourAccountName\AppData\Roaming\SoundSpectrum\G-Force\Scripts // Newer, Shift('R') and Shift('W')
Naming Convention: 'CTRL [A-Z].txt' // WORKS - but Numbers NO LONGER Supported
Naming Convention: 'Key [0-9A-Z].txt' // Original Format - WORKS
Naming Convention: 'Key [0-9A-Z].py' // Python format - Currently NOT executable
The 'Shift W [0-9A-Z]' generates a Python script (NO semi-colons - yech!) in the Newer Repository,
that currently is NOT UNDERSTOOD by G-Force (when tried to be executed)
The 'Shift R [0-9A-Z]' trys to find, and run a 'Key [0-9A-Z].(txt|py)' script file in EITHER location.
'Key [0-9A-Z].txt' generally WORKS
'Key [0-9A-Z].py' FAILS
'Set [1-5]' (menu buttons) is the Same as 'Shift W [1-5]' // BROKE, 'cause Shift W' generates '*.py'
// Kills all overlays with a matching ID to the one given.
void KillOverlay( int inOverlayID ); // WORKS, but seems to REQUIRE 'inOverlayID'
feel free to call me out on any of my errors...
Scripts would be FAR EASIER to maintain IF timing specifications could also be specified as:'. + 00.00' // NOW Plus Offset
