Kill process without killing JMP

[nathan-clark]

JMP does an amazing job of chugging along so even long analyses get done eventually (unless there are hardware limitations). However, sometimes these long processes are kicked off on accident or without realizing how long they will actually take.

I would like to suggest a way to kill the current process so the single thing I started stops, but I don't have to force close all of JMP and lose any other work I have going on. I know myself, and many colleagues, have done these things - from an accidental click to a botched while loop - so a way to save JMP from this 'killer process' would be greatly appreciated!

[nathan-clark]

I wouldn't say Esc is the death sentence for all stuck code, but it's definitely the first thing to try.

Personally, I've never had any of my stuck code killed by the esc key

[altug_bayram]

Somehow related to the submitted wish request -Of if not, perhaps it could be considered as an independent wish request

Sometimes an expensive analysis may be kicked off (intentionally or not) that the user may not prefer to wait to completion.

A way to simply return an estimated time to completion : XXX mins .. confirm ? ..  could give the user the extra option to launch the analysis or not. 

[hogi]

@altug_bayram that's a nice idea

a somehow related idea: 

define a timeout for platforms in the preferences: Timeout