I’m batch processing files with a pipeline of scripts.
Every now and then there is a unhandled exception and I get a dialog something like this:
@stevebaer I think you are the one to ask if there are means to handle this without a full stop.
Ideally I’d have an option to set what to do in case of such an event.
In my case, I would like to collect the Traceback, write it to a log file, Save the file and shut Rhino down then. Best would be to proceed to the next file for processing but by means of starting a New Rhino instance that can pickup where it stranded.
In short a custom handling of unhandled exceptions.