I first used AHK for macros in games. The scripts can even read pixels on the screen, play sounds or beep, execute programs, send mouse click/events. And of course send keyboard keys.
It is great for automating things.
AutoHotKey V2 (Breaking Upgrade)
21–30 of 124 posts
Re: AutoHotKey V2 (Breaking Upgrade)
#22This is a bit of a PITA for me as most people use AHK to handle shortcuts for komorebi[1], which led to me generating an AHK library[2] to help people write their configs. Turns out every single line of that generated library (not to mention the entire sample config for newcomers) is now invalid syntax in v2. I'm taking a month off from development while I'm traveling, maybe I'll feel less salty about this when I get…
Can you just specify AHK1 for users for the time being? Is there an equivalent of a shebang, differentiator, or something in AHK scripts that'd allow a simultaneous v1 and v2 install? When Python went from 2.x to 3.0, there wasn't some expectation that all adoption of breaking changes happen immediately - one hopes similar provisions have been made here.
Re: AutoHotKey V2 (Breaking Upgrade)
#23if the breaking upgrade thing is such a problem I guess it should be possible to run both versions side by side, although might require some registry tweaks?
It's trivial to run both side by side. You can easily switch between interpreters.
I expected, just a few people seem especially upset about the upgrade breaking their scripts.
Re: AutoHotKey V2 (Breaking Upgrade)
#24AHK is what keeps me on Windows
Keyboard Maestro for macOS is great although it's not free like AHK.
Re: AutoHotKey V2 (Breaking Upgrade)
#25I like AHK very much but its scripting language is difficult to use of you do not use it often.
The most complicated pay for me are braces and delimiters: I never know when to use a brace, when to use style #-delimiters (#HotIf for instance), when a mineral is enough, etc.
It would be much better if there was a decision to be homogenous and always require braces, or newlines or whatever - but always the same thing.
Re: AutoHotKey V2 (Breaking Upgrade)
#26I like AHK very much but its scripting language is difficult to use of you do not use it often. The most complicated pay for me are braces and delimiters: I never know when to use a brace, when to use style #-delimiters (#HotIf for instance), when a mineral is enough, etc. It would be much better if there was a decision to be homogenous and always require braces, or newlines or whatever - but always the same thing.
I personally use AutoIt a ton as a super fast way to quickly prototype GUIs. It's basically a really simple entrypoint for WinAPI.
Shameless plug: my script for emulating a trackball with your keyboard [0], and my tray app for quickly tweaking your cursor speed (usually for when I'm drawing something)[1]
There are also some really useful utility apps like WhyNotWin11[2] that's made entirely using AutoIt
[0] https://github.com/EsportToys/TPMouse
[1] https://github.com/EsportToys/MouseTray
[2] https://github.com/rcmaehl/WhyNotWin11Re: AutoHotKey V2 (Breaking Upgrade)
#27The bit about the anti-malware is sad. Does anyone remember a true positive from their AV? I can recall countless incidents caused by false positives, but can’t remember a single true positive. The latest was Crowdstrike Falcon (AI POWERED!!1) flagging signtool.exe as malware. The one from the Windows SDK. By Microsoft. Signed with Microsoft keys.
Security is hard. It is only when you have to fight never ending scenarios from multiple users that you understand how limited a product that helps you is.
Crowdstrike helped us a few times to contain serious issues, and made me difficult for people as well because it blocked their "suspicious" behaviour.
The bad guys only need to succeed once.
Re: AutoHotKey V2 (Breaking Upgrade)
#28AHK has the distinction of being an absolutely indispensible tool and a horrendously terribly designed language. It's probably the worst-designed programming language I've ever seen. Whenever I'm frustarted with how slow and conservative Python development is, I remind myself that this is the main thing keeping us from reaching the same state as AHK. I hope that this upgrade will fix some of these problems. I'll prob…
> It's probably the worst-designed programming language I've ever seen.
I always wonder in these discussions why bourne shell/bash gets a pass. Many people know it, but are somehow blind to how terrible it is.
Re: AutoHotKey V2 (Breaking Upgrade)
#29This is a bit of a PITA for me as most people use AHK to handle shortcuts for komorebi[1], which led to me generating an AHK library[2] to help people write their configs. Turns out every single line of that generated library (not to mention the entire sample config for newcomers) is now invalid syntax in v2. I'm taking a month off from development while I'm traveling, maybe I'll feel less salty about this when I get…
As far as string interpolation goes, what's wrong with the format() function? It was already in v1, and hasn't gone anywhere in v2.
Re: AutoHotKey V2 (Breaking Upgrade)
#30AHK has the distinction of being an absolutely indispensible tool and a horrendously terribly designed language. It's probably the worst-designed programming language I've ever seen. Whenever I'm frustarted with how slow and conservative Python development is, I remind myself that this is the main thing keeping us from reaching the same state as AHK. I hope that this upgrade will fix some of these problems. I'll prob…
[deleted]