Hello there! o)
I have really huge "speed" issues with DO on my main machine for some time (months). Everything is chewing gum, switching folders takes 2 seconds, tabs open in slow motion etc. This is something I can hopefully resolve with you in another thread.
Here, I'd just like to post the idea of some scripting fall back handling, this is something I wished was possible multiple times now (for debugging scripts or investigating other weird effects - like now).
Because: If you have several buttons in use which use scripting and you disable scripting for testing purposes, DO renders into a useless brick for me. I can't go up a folder by double clicking the lister background, because I call a script-command there. I also cannot delete, copy or move, because I use a script command there (for logging etc.). So once I disable the scripting, my DO config is basically useless and I cannot test stuff with it in this state.
ListerDoubleClick (command not found)
I was thinking of a modifier like @noscript or similar, which in case the scripting is disabled, would run the regular/default button code instead of the script function. It might also make sense to be able to disable scripted events separately and keep the script commands going, since these are required to keep the GUI working.
What do you think?
BTW: If you click the "disable scripts" button in the prefs, there is no indication that something changed. The button does not change and the display of the scripts does not change either, you need to re-enter the prefs dialog to see the scripts being greyed out.