AutoHotkey Community

Because the point of stop-all is to exit the thread, not pause it.

I achieve the same thing in my single simple script using Reload, as it stops all threads in my script.

I'm not sure whether this is bad practice or dangerous, as I am a complete novice, but it works for me.

I too use Reload, usually to recover from a misbehaving script. Even if it's not stuck in an infinite loop, it might be going down a wrong path and I want to stop it.

The downside to Reload is that it wipes the global variables and re-executes the autoexecute section. For me this is not a big deal but I can imagine scenarios where this would be a problem and Reload would not work.

It also desrtoys all the guis. So if you have one that is active, it will flash, which is not very appealing.

+1 for the wishlist. Reload is a workaround, Pause is a workaround.

There should be a command that kills all running threads.

How about change Exit to take a parameter which is the number of threads to exit, including the current one.

E.g.Pressing Esc would exit the current (interrupting) thread (the one started by the Esc key) and the one directly underneath it (the one it interrupted), i.e. the loop.

_________________
Scripts - License

+1 for this wish.
I need this functionality for my ahksandbox.
ahksandbox already prevents all insecure commands and functions, but is still vulnerable to denial of service via infinite loops.
the ability to kill all threads would allow the host script to do that after a time out for misbehaving scripts in the sandbox.
Will probably butcher the source to make it work one way or another...