Errors occuring in Diadem user commands result in all running scripts aborting without any clear sign of the reason. The only means to find out is the log file in Diadem Script.
Support says this in a feature, as user commands are supposed to handle events and there should be no (frequent) error messages.
On the other side, user commands are the ideal place to have a user functions library as it is accessible from everywhere including dialogs. With ScriptInclude command such a library has to be included at every script start and possibly several times as dialogs have a separate script environment.
Therefore I would welcome an option to turn on error messages / beep when there is an error in user commands.
The current behaviour of silent abortion of any script is quite confusing, especially for people that are only applying scripts for evaluation.
