Script timeout -- why have them?

The scripts run by the GUI (pre-connect, connect and disconnect) have associated timeout values in the registry. Out of these only the connect script timeout is used in any real sense (to report a timeout error that is ambiguous), the rest are just used for sleeping for that many seconds for no apparent reason.

I would like to clean up these, and run the scripts in their own threads, but wonder why the timeouts are there in the first place. The wait in worker thread just causes the status window to go non-responsive, especially for scripts that may take several seconds to complete. None of the scripts are force-terminated after timeout so it seems we can get rid of those waits altogether. Or increase those to fairly large values to be used to terminate run-away scripts...

Any thoughs?

Start by tracing how the GUI runs the pre-connect, connect, and disconnect scripts, where their registry timeout values are read, and how the worker thread updates the status window. Resolve whether the waits should be removed or whether timeouts should terminate runaway scripts; the issue needs a maintainer decision before implementation can be considered done.