search

me2d13 / luamacros

665 stars 87 forks source link

Default keys and programmed keys fire up #31

Open ReapersDragon opened 6 years ago

ReapersDragon commented 6 years ago

After a longer time running LuaMacros ( a couple of hours) it sometimes happens that when a button is pressed the default key of the keyboard is send to the running program and also the programmed shortcut is send. So for example if you have a editor running and have something marked and have at num7 the key combination ctr+f for search it rewrites the marked text by 7 and also sends ctr+f after this to open the search dialog. Only a restart of LuaMacros corrects this behavior. Sadly I cannot say why this happens and why it sometimes happens after 1 hour and sometimes it is not happening in 8 hours.

me2d13 commented 6 years ago

Hard to fix without way to reproduce it. If you find some case when the blocking always start working, please update the issue.

Scrxtchy commented 6 years ago

I've had this issue a number of times over the years of using luamacros too Replication unfortunately is really just hit and miss over regular usage. But granted it's really hard to understand why the issue occurs, since I don't think it's the program's fault entirely, but something else on a system that causes luamacros to fault

blumberg commented 5 years ago

I'm experiencing same issue as well. For a few months I couldn't find a way to reproduce the issue. Yesterday I found a way to replicate. If I use second keyboard within a PDF File Reader (Adobe Reader XI, Version 11.0.10) the blocking stopping works and I need to restart Luamacros. Another think that I don't know if is possible to fix is CAPS LOCK, it never gets blocked.

HydraheadHunter commented 2 years ago

I got the program working, thanks to a tutorial somewhere, but I restarted my computer because it was yelling at me to update (the update failed like it always does), and now this problem is persistant: it still executes the commands, but it also sends the original key. Restarting LuaMacros does not solve the problem.

Edit: the program I was using to test my keyboards functionality apparently somehow changed from a normal program to one of the programs using the lower-level functionality that luamacros can't stop from communicating with: I say this because my aux keyboard worked in that program as intended but no longer does, but it still works in other programs. So, probably, I'm just an idiot; but maybe this problem is someway rooted programs that normally behave changing into that lower level state and getting stuck, or luamacros thinking that's it's a lower level program, and not properly injecting it's code because of that.