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
I'm posting this as I was at first utterly baffled when trying to make a hotkey combo of meta and plus, and the docs did not lead me in the right direction. It was only when I put some logging inside the lib itself that I realised I really wanted the equal key and that my desired hotkey could be described as meta+equal (complementing my meta+minus key that worked fine).
I suspect this is a common mistake that devs who don't normally work with a lot of hotkeys (such as myself) forget that keys should usually be nominated by their standard function and not their modified function.
If the docs could be updated in a way that highlights this pitfall I think it would save a lot of issues being filed for hotkeys that don't work :)
The text was updated successfully, but these errors were encountered:
I'm posting this as I was at first utterly baffled when trying to make a hotkey combo of
meta
andplus
, and the docs did not lead me in the right direction. It was only when I put some logging inside the lib itself that I realised I really wanted theequal
key and that my desired hotkey could be described asmeta+equal
(complementing mymeta+minus
key that worked fine).I suspect this is a common mistake that devs who don't normally work with a lot of hotkeys (such as myself) forget that keys should usually be nominated by their standard function and not their modified function.
If the docs could be updated in a way that highlights this pitfall I think it would save a lot of issues being filed for hotkeys that don't work :)
The text was updated successfully, but these errors were encountered: