You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a big issue here, just letting you know it in case it actually is a bug.
When holding windows (because I use windows keyboard shortcuts a lot) the edit field function is enabled (just as with Ctrl), so basically Win seems to be imitating Ctrl.
I don't think it is intended? Because even though having an alternative button maybe is necessary for some people the Win button initiates the start menu, so it doesn't seem so useful.
The text was updated successfully, but these errors were encountered:
Thanks for the report! I didn't know of the problem because I use a Mac. I looked into it, and yes, it's not an intended behaviour, but it's not easy to fix it because reasons.
If you are interested in the reasons why, it's because of Macs: In macOS, the usage equivalent of Windows Ctrl key is the Command key. So the add-on detects Ctrl key as well as the Command key so it works in both OS.
But in code, Windows Ctrl key is the same as Mac Ctrl key, and Mac Command key the same as Windows Win key. So when it's listening for Command keys in Macs, it also listens for Win keys in Windows. And it isn't simple to detect which OS it's running on. Since I don't think it's a serious problem, I'll just leave it as is.
Not a big issue here, just letting you know it in case it actually is a bug.
When holding windows (because I use windows keyboard shortcuts a lot) the edit field function is enabled (just as with Ctrl), so basically Win seems to be imitating Ctrl.
I don't think it is intended? Because even though having an alternative button maybe is necessary for some people the Win button initiates the start menu, so it doesn't seem so useful.
The text was updated successfully, but these errors were encountered: