search

spyoungtech / voice-commander

cross-platform voice-activation hooks and keyboard macros
MIT License
6 stars 0 forks source link

Is this compatible with AHK version 2? #12

Open gtusr opened 1 week ago

gtusr commented 1 week ago

The reason I ask is because AHK version 1 is now officially deprecated and will only be receiving limited maintenance fixes from Lexikos for the foreseeable future.

Microsoft is also planning to remove the old and venerable Windows Speech Recognition engine from Windows in a future release of the operating system. It's scheduled to be replaced with the newer Voice Access feature, which unfortunately does not appear to support API level access.

Fortunately the Python SpeechRecognition package does not depend on Microsoft's soon to be deprecated WSR SDK.

Hence my interest in this project.

spyoungtech commented 1 week ago

I haven't explicitly tested against AHK v2, but I'm happy to support it. There may be some tweaks needed or maybe some features needed to accommodate the behavioral differences and different defaults in v2, I'm not sure.

If you have any trouble using v2, let me know and I'm happy to fix anything that's not working the same as when using v1. I'm also happy to accept contributions to add better support where needed.

Right now, I don't think there's any configuration yet that would allow you to specify v2 as the engine in code, but if you set the AHK_PATH environment variable (or patch it into os.environ) to the path of an AHK v2 executable, or just have AutoHotkey.exe on PATH, that should work.

That said, I don't think AHK v1 will necessarily stop working anytime soon. Eventually, my upstream ahk package will use v2 as a default. But for now, v1 is the most stable and well-tested on the upstream side of things.