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 wonder if it's possible to support the dynamic toggling of NKRO.
This is an important feature for multi-language macOS users because macOS has problems handling CAPS when NKRO is enabled.
More specifically, macOS has a feature that supports switching the input method from and to U.S. by a short press of CAPS, and a long press of CAPS will lock all input to uppercase. But when NKRO is enabled, a short press of CAPS will be interpreted(by macOS) as both a short and long press, and thus macOS will switch the input method and then lock the caps.
More discussion can be found in an issue in the upstream qmk_firmware repo: qmk/qmk_firmware#15178.
I build the firmware on my own to disable NKRO in keyboards/system76/launch_1/rules.mk, but this will also disable system76_ec_eeprom_op in keyboards/system76/system76_ec.c because eeprom_update_block/eeprom_read_block is only defined when ENABLE_NKRO = yes. Disabling system76_ec_eeprom_op will make the configurator unable to save the LED configuration(but the keymap is fine).
Hi,
I wonder if it's possible to support the dynamic toggling of NKRO.
This is an important feature for multi-language macOS users because macOS has problems handling
CAPS
when NKRO is enabled.More specifically, macOS has a feature that supports switching the input method from and to U.S. by a short press of
CAPS,
and a long press ofCAPS
will lock all input to uppercase. But when NKRO is enabled, a short press ofCAPS
will be interpreted(by macOS) as both a short and long press, and thus macOS will switch the input method and then lock the caps.More discussion can be found in an issue in the upstream qmk_firmware repo: qmk/qmk_firmware#15178.
I build the firmware on my own to disable NKRO in keyboards/system76/launch_1/rules.mk, but this will also disable
system76_ec_eeprom_op
in keyboards/system76/system76_ec.c becauseeeprom_update_block/eeprom_read_block
is only defined whenENABLE_NKRO = yes
. Disablingsystem76_ec_eeprom_op
will make the configurator unable to save the LED configuration(but the keymap is fine).Based on the qmk_firmware wiki, NKRO should be able to be disabled dynamically: https://github.com/tmk/tmk_keyboard/wiki/FAQ#nkro-doesnt-work. But the
Magic
N command doesn't seem to work on the launch firmware.If it is possible to support this feature?
Cheers!
The text was updated successfully, but these errors were encountered: