The issue that @ale2x72 is running into ties directly back to the ongoing discussion here:
Close GH Player definition - #21 by kiteboardshaper
TL;DR:
McNeel/Rhino has introduced tooling to compile Grasshopper definitions into YAK-deliverable plugins — which is great. However, these tools were built with a “run once and exit” execution model in mind.
For those of us looking to build persistent or semi-interactive tools, this presents a problem. In Rhino 7, there were some workarounds (e.g., using the Remote Control Panel). Rhino 8 introduced the “keep open after script completes” option, which helps — but what’s still missing is a clean way to intentionally exit or shut down a compiled Grasshopper plugin.
At the moment, there’s no reliable or tidy way to programmatically close or exit a GH script that’s running in this compiled plugin context.
So I’ll ask again:
Can we please get a “Terminate/Exit Compiled GH Script” component or method?
Would really help with building more robust, user-driven tools in this new plugin model.
Cheers,
DK