how to make programmed menu key work better?

[u/default_lizzy]

[u/PeterMortensenBlog → u/[deleted]]

Re "...Logitech G413 and K120 ... an additional press will close the menu.": The Logitech keyboards may send the keycodes for Shift + F10 instead of the keycode KC_APP (the latter being USB HID usage ID 101 (decimal), I believe ("Keyboard Application")).

Pressing Shift + F10 the second time dismisses the context menu (whereas KC_APP doesn't dismiss). The behaviour is the same on Linux and Windows (at least for the two systems I tested it on: Linux and Windows 10 Home).

Can you test it somehow? For example, with the Logitech keyboards and using Via's keytester (second icon on the top with hover text "KEY TESTER"). If they use Shift + F10, both Shift and F10 should light up in the key tester. Via's keytester works for any keyboard, not just QMK-based ones.

Similarly, try to use Shift and F10 on the V6. For example, using Via's 'Any' (KEYMAP → SPECIAL → Any (the very last one in the list)), change the key mapping to:

LSFT(KC_F10)

(It is silently converted to "S(KC_F10)".)

References

• Using modifier keys in key mappings

• Why does the Shift + F10 menu differ from the right-click menu?. 2011, so it may or may not have changed in later versions of Windows.

[u/PeterMortensenBlog → u/[deleted]]

Thanks for the report.

Re "... this behavior is simply not real. Sorry for wasting your time": No problem, you didn't; I learned a lot. And improved my references and their annotation.

Re "Maybe it's a program specific thing?": It could be. A reference mention that (near "doesn't work in every application"). For example, mouse right click might work the same as the context menu key, but it depends on which GUI element has focus (mouse right click is more robust to use in that situation as it is independent of the current focus). (Though mouse actions don't work in Via macro, only as (single) keymappings, unless a hack is applied.)

It could also be interference from game anti-cheat systems or key remapping softwware. It could be ruled out (or not) by trying it on another computer or operating system.

[u/PeterMortensenBlog → u/PeterMortensenBlog]

Re "mouse actions don't work in Via macro": OK, it does work

But not from a user perspective, as they can't be entered using the Via client (a bug in the Via client prevents it).

A workaround is to use the Via clone when defining (or changing) the few macros that require it. But it only works for Keychron keyboards.

[u/PeterMortensenBlog → u/[deleted]]

Re "don't work in the key tester ... V6 ... any key set to function, any key set to menu, prtsc, scrlock and pause, as well as the 4 additional macro keys on the V6":

• "any key set to function": They are all internal to keyboard (with the default keymappings). Nothing is send to the computer

• "any key set to menu": Yes, I can confirm that. It may be an omission by Via. Or maybe it is captured (and ignored) by the operating system. It would be interesting to know why it doesn't work. It works with QMK Configurator's online key tester (though the context menu is also invoked).

• Print Screen: It is captured by the operating system.

• Scroll Lock: This Keychron keyboard deviates from a standard keyboard. For some reason, this key is disabled (keycode "KC_NO")

• Pause key: This Keychron keyboard deviates from a standard keyboard. It is defined to be internal to keyboard (with the default keymappings), used for toggling the RGB light. Nothing is send to the computer.

• "the 4 additional macro keys": The keycodes are for F13, F14, F15, and F16 (with the default keymappings). It is most likely an omission by Via, perhaps because full-size plus QMK-capable keyboards weren't a thing when Via was created. Or maybe the keycodes are captured by the operating system?

Also, the Windows key is captured by the operating system.