New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Win+l shortcut doesn't work #896
Comments
This seems to also be an issue with AutoHotkey which makes me think it's a Windows limitation. The AHK answer is to use the following AHK script, which you can then trigger via an Optikey shortcut. .ahk script: F20::
DllCall("LockWorkStation")
return Optikey keyboard: <DynamicKey>
<Label>Lock</Label>
<Action>F20</Action>
</DynamicKey> ref - https://stackoverflow.com/questions/42314908/how-can-i-lock-my-computer-with-autohotkey Alternatively, keep nagging me and I'll write an AHK plugin for Optikey so you don't need to use up intermediate shortcut keys :-) |
How OptiKey was being used
Dynamic keyboard, DirectInput gamepad trigger (have also tried standard keyboard and dwell trigger, same behavior in both cases)
I selected the win key and then the l key.
What the user expected to happen
Windows should lock the screen.
What the user actually experienced
The letter 'l' was typed in the target application. The screen did not lock.
Version
Steps to reproduce the issue
Any other information that helps to describe and/or reproduce the problem
I have verified that win+l does lock the screen when using a physical keyboard.
Some other win shortcuts do work, e.g. win+v for clipboard history (requires enabling clipboard history in Windows settings)
The text was updated successfully, but these errors were encountered: