AutoHotkey Community

[infogulch]

Wait, ms EDIT: this would pretty much be useless. /EDIT
Could allow other threads to run instead of stopping the entire script like sleep does. (other threads could be started by: hotkey, gui, menu, timer)
Like Keywait: Maunal Wrote:While the command is in a waiting state, new threads can be launched via hotkey, custom menu item, or timer.

Thread, ContinueInterrupted [, False] (needs shorter name )
A setting (like DetectHiddenWindows) that, if the current thread interrupted another, whenever it encounters a Wait or KeyWait, it goes back to the interrupted thread and continues execution until the *Wait is over in which case it interrupts agian to finish. (Of course, it would not apply to GoSub or a function call as they aren't new threads, but a branch of the current thread.)


Ok, that may be a little confusing, so here's a conceptual example:

[Lexikos]

When a new thread starts, the current thread's settings are saved into a structure allocated on the stack. This means that the current thread cannot resume until the new thread finishes.

I think that while the feature you are suggesting would be an improvement, it would require fairly major changes to the way threading works. True multi-threading support would likely require similar (and more) restructuring, but would be more powerful.

[infogulch]

I see. That's too bad. EDIT: Uh, nvm. /EIDT What about a plain "Wait" instead of "Sleep"? That would allow timers, hotkeys etc to run while it's waiting, instead of completely stopping the whole script.

Do you think ContinueInterrupted a good enough idea to implement when multi-threading is added? Since it would require similar restructuring..

_________________
A great Beginner's Tutorial

[Lexikos]

[infogulch]

Sleep:
Omg, that completely missed me, sry. I guess "wait" wouldn't do anything but add another command. (but you're always looking for more complication right? )

Thread, ContinueInterrupted:
Currently, if an interrupting (hotkey/timer) thread stops (sleep/keywait), the thread it interrupted is stopped too.
This command would allow that thread that was originally running to be restarted and execution resumed in it. (until the stopped thread is done waiting)

Why? it keeps the script moving and working, so if there's are lines to be executed in a different thread, they aren't hindered, using more of the script's allotted cpu time.

I'm thinking maybe the thread's priority could affect wether it goes back to the interrupted thread, on a per thread basis. E.g. if an interrupting thread with a higher priority than the one it interrupted encounters a sleep, it doesn't go back to the previous thread...
Just throwing around ideas.

Thanks for being patient with me.
_________________
A great Beginner's Tutorial