end process button for idiots

Will be great to have a End Process button in grasshopper, something similar to Esc in rhino to cancel the operation in progress

Sometimes as a good idiot i don't realize that some inputs are graft and others are flatten, right now i'm in front of the computer completely stacked, with a mirror process with more than 3000 objects and the same number of planes but graft ...... and i haven't saved in a while

of course the simplest solution is to take care before performing those actions that consumes a lot of ram, but yo cant underestimate the stupidity !!!!!

Praying to the Computers god !!!!!!!!!

Replies to This Discussion

Permalink Reply by Nik Willmore on June 27, 2015 at 12:07am

Sometimes you can get a command-S save done anyway, and sometimes you can switch over to Rhino and issue a command-W (zoom) which temporarily stops Grasshopper but rarely lets you get back to it without it locking up again.

I'm told we have to wait for Grasshopper 2 wed to Rhino 6, in months or years from now since Grasshopper isn't multithreaded. It does look for the escape key but not reliably at all.

Here is a response from the developer to my same sort of question:

http://www.grasshopper3d.com/forum/topics/emergency-top-for-solutio...

David Rutten: "if it was doable, I'd do it, but Grasshopper runs on the main UI thread which means that no key presses come through until the process is done. Right now I check for escape key state (circumventing the key-press events) at certain points during the solution, but the more I check the more I slow down the solution, and there are large areas where I can't check because it's not my code that is taking up all the processor power in the UI thread."

I solved my own problem in that case by leaving the solver disabled in the menu and then invoking it manually as a recompute menu command that works once anyway. That won't help you with a rogue script though, but will let you set things up without Grasshopper recalculating each change.

With the solver disabled, when you have to manually invoke a recompute, that necessary action can help remind you to save first.

I tried assigning the Rhino command GrasshopperUnloadPlugin to F4 in Rhino settings but in the test case of populating a box with 1000000 random points (Vector > Populate 3D), the freeze up cannot be ignored as you access Rhino, which remains grayed out as a program even when you highlight its window, and nor can you get any Grasshopper command-S in while its running forever. That's only the equivalent of 100X100X100 points yet it still locks up Rhino so long. Thinking in this very simple case clarifies things, since it it won't let go then complex scripts may have some better chance but really the problem is in the system itself.

At least the Rhino close box works, so you don't need the Windows Task Manager :-).