Win{L} bug?

[drivermix]

Hello,

For my needs, I was trying to set up Win{L} shortcut, and ran in this problem.
I'm on Windows, and first had to disable Windows' native Win-L shortcut (Lock Workstation feature) in registry.
You can find the registry fix here: https://superuser.com/questions/1059511/how-to-disable-winl-in-windows-10

keymapper config looks simple:

Win{L} >> Delete

Now, hitting Win{L} does trigger the Delete key, but after I'm done using the shortcut, the Win key remains stuck... until I press it again. I tested another Win{key} combo, like Win{J}, and it works as expected. Additionally, I disabled keymapper to see if hitting Win-L on its own would cause the Win key to get stuck, and it looks like the issue lies specifically with keymapper.

Anyway, I hope it's something that can be fixed in the next update, and isn't a Windows limitation.

Thanks in advance!

[houmain]

keymapper does not handle Win{L} specially. So, I doubt that anything could be done. Maybe the shortcut is still interpreted on a lower level, even when locking was disabled. But I will try it myself soon.

[houmain]

OK, I tried the DisableLockWorkstation registry key with this configuration:

Win = Meta
Win{I} >> ArrowUp
Win{K} >> ArrowDown
Win{J} >> ArrowLeft
Win{L} >> ArrowRight

Unfortunately the registry key does not disable the special behavior of Win-L: As soon as the L of Win{L} is pressed, Windows registers the Win key (even when suppressed by keymapper) and only unregisters it when the Win key is physically released (even when keymapper tries to explicitly release it).

So, the best thing one could do, is to prevent any input after Win{L} (which would trigger unwanted shortcuts), until the Win key is physically released:

Win = Meta
AfterWinL = Virtual
AfterWinL{!Win} >> Win{F12} !AfterWinL
(AfterWinL Win){Any} >>

Win{I} >> ArrowUp
Win{K} >> ArrowDown
Win{J} >> ArrowLeft
Win{L} >> ArrowRight AfterWinL

When the Win key is released Win{F12} is tapped, which does nothing but reset the state of Win, since tapping Win alone would open the start menu.

[drivermix]

Thanks for looking into this, and confirming that it's an inherently problematic combo. In light of that I have decided to rework my home row shortcuts strategy to avoid using Win{ }.