In Ruby
UI.openURL(your_path_to_batch_file)
runs a Windows "batch file" (.bat, .cmd etc or compiled stuff like kix or VB)... I'm sure there'll be equivalent UnixShell or AppleScript possibilities for the Mac - I think that, unlike PCs, Macs get a full install of Ruby, so perhaps for Mac this could even be implemented in Ruby outside of SUp ? ... However, there is one big problem with this... IF the batch file you run changes the SUp registry settings during a Sup session it's pretty much pointless - most of these values were read when you started SUp and will be rewritten when you exit SUp - therefore most of these changes you have reset within SUp wouldn't make any difference - they be ignored during the current SUp session and then lost as you exit SUp when it rewrites things.
To reset the registry values you need SUp NOT to be open... BUT Ruby needs SUp open to carry on working.
However, it could be made to work this way...
A 'SaveToolbarsSettings' Ruby script would run suitable batch files to make the required files with the info extracted from the registry (or ini file for Mac ?) - all as outlined by CadFather - you could run this script at any time to make a backup of the current 'good' setup...
A 'ResetToolbars' Ruby script would first save the model's path details to a temp-file - note: that if it were an 'unsaved' model you would be prompted to save if - if you cancelled the model would be discarded and the temp-file entry set to "".
The script would then run a batch file.
This batch file would wait (looping) while SUp was open (using plist etc ?).
Assuming you didn't initially have an 'unsaved' model, then the script would save the model.
The script would then close SUp (model.close_active ? or another 'process-killer' batch file ?).
The batch file would then notice that SUp was no longer running and so it would re-start - it would rewrite the registry values for the saved toolbar settings - again, all as outlined by CadFather.
Finally the batch file would reopen the model using the temp-file info that was saved at the start - note: if it was an 'unsaved' model then SUp would simply opene from the default template, with a new 'unsaved' model file.
SUp should now continue to reopen with the toolbars setup as they were previously saved from a 'good version'...
This way could effectively automate saving and resetting of the toolbar setup - accessed within SUp itself, initiated with Ruby, running external commands - however the coding needed extra-ruby for PC and/or Mac is not that easy - but I'm sure it's do-able...
I don't have the time (or the patience !) to look at this right now... but perhaps CadFather or someone else could automate this furthe, using these ideas ?
