Ad blocker detected:
Our software and support is 100% free. This website is not.
You can donate in 2 ways, by turning off your ad blocker or by pressing the Donate button.
************ NOTICE ************
UPDATE YOUR BOOKMARKS!!!
We have an issue that there is no way around as of yet.
I have done all I can to try and prevent this from happening.
We are going to be losing the .com, .org and .de domains.
We have not been able to contact the original author of EventGhost
(the person that owns those domains) to redirect them to the new web server.
I set in motion when we first moved a redirection from the old server to the new server.
I also put in markers so that search engines would see this change and update any pointers
they have. We still have the .net domain for the production site. and the .rocks for the test site.
For the past few months you have been getting redirected to the .net site if you used one of the 3
domains mentioned above. I just wanted to tell everyone so they can make any changes needed.
I have recently started to notice weird issue: Whenever combination containing LWin key is captured via this plugin (for example LWin+Num0 triggers this bug reliably), shift key will become stuck (for example any click I perform after that combination it would be have as if I would shift + click it). Pressing actual shift key un-stucks the key.
This does not happen with RWin interestingly, does not happen if combination is capture (not added to any macro) and does not happen if Keyboard+ plugin is disabled.
The stock Keyboard plugin is notorious for this, but I've never ever seen it with Keyboard+, and even with LWin+Num0 (which is one of the combos I most frequently use), I'm not able to reproduce. Is it possible your macro or the program you're launching is the culprit? Try moving the event to a different macro. If that doesn't help, unless you can come up with a set of reproduction instructions that work for me, I fear there's little else I can say.
Well it is obviously a DLL or some other component missing. But I don't remember ever installing any additional component when installing this plugin, just grabbing source from github, replacing old Keyboard plugin and it worked.
That is interesting. Will EG eventually run on Python 2.7?
Regarding my previous issue, reinstalling did not seem to help. Even creating empty macro and adding LWin related event is enough to trigger this bug. I guess I will try a bit and report back if I can figure out what exactly could be related to it.
Events are then forwarded to the same exact macro as before.
Wow you saved me Matejdro, thanks a lot for the script. I've been trying to get this useless Keyboard plugin to work in conjunction with AHK but was impossible. Your event sending script works like a charm for sending whatever it is to EG and then using those events for my Hue plugin.