due to some automation task I’m often restarting Rhino and Grasshopper from a script using
/nosplash /runscript="-grasshopper editor load document open file.gh _enter file.3dm"
Everything works okay so far. Though I do receive Grasshopper error messages (GH breakpoints etc) sometimes that I just can’t resolve. So they’re ignored and if Grasshopper becomes unresponsive, a background host application force quits and restarts Rhino and Grasshopper.
However, I wonder if there is a setting to rudely and forcefully inhibit Grasshopper error messages and warnings?
Specifically the “Potential Plugin Crash Protection” warning upon startup blocks my Grasshopper from being reloaded
Further there are the mentioned Grasshopper breakpoint messages, that I’d like to not receive, but that’s not soo important, as I can just keep ignoring those:
Does anyone know of a way or configuration to do that?