|
|
|
|
|
by inafewwords
1030 days ago
|
|
Every AHK I've made has gone rogue because I want it to do things and it does it well but without guard rails i overwhelm my target every time. Thankfully the target is usually my local and I just mostly reboot You'd think I'd learn but my scripts usually start small for with one specific use and i enlarge it Unsafely once I think of another use for it Loops are my danger zone. After a few crashes the first guardrail I end up adding to a script is a stop key combo interrupt. Then figure out what bounds to put only after every mistake. I don't have the foresight to prevent "rogue" behavior |
|
To avoid [infinite loops] add the $ prefix to the hotkey definition (e.g. $^c::) so that the hotkey cannot be triggered by the Send command.
or a very restrictive #MaxHotkeysPerInterval