microkeys VS protothreads-cpp

I wrote MicroKeys[1] out of a similar frustration. Granted, I never got past the POC stage, so it's not as feature rich as AHK, but it solved a very specific itch I had. I debate if I should flesh it out further, or try using AHK again.

[1] https://github.com/seligman/microkeys

And with a little bit of coercing, it can be used the other way: To embed Python in Desktop apps giving you a fairly light-weight Python interpreter.

I used it for a little Windows macro program ( https://github.com/seligman/microkeys ) . I got it to a POC stage to solve the precise problem I have, basically I needed to be able to do some simple text parsing on whatever's in the clipboard and type out the results, so I'm happy. I'm always curious if it potentially fills a need for others as well.

I'll join in:

I'm building a tool called MicroKeys. It's a macro program, for Windows right now. It uses MicroPython as the script engine to let you register hot keys that do things. It's very much a work in progress right now.

I'm writing it to fill a very specific niche I have, but if it's useful to others, I'd love to hear feedback on what it could do to be better to help it come to fruition.

https://github.com/seligman/microkeys

I'll be working to progress MicroKeys, my Windows MicroPython based macro program. It's ready for others to play with, if barely, but I do need to work on how it handles exceptions, and improve the debugging experience a bit.

I'll be working on progressing my MicroKeys project, a way to create macros for Windows and declare them using Python.

For a while I've been working on a little pet project, MicroKeys. It's a Windows app that embeds MicroPython, allowing the user to create macros that run Python functions in response to keys. The GIF on the readme shows the basic idea, when I hit Alt-Z, it runs the function and types out the result.