[SOLVED] Disable/remap Framework "gear" key

[MJ1]

@Niko_Ortner

When I click on the “Any” mapping in the “Special” section, the prompt is pre-filled with what corresponds to the last key that I clicked. The F12-key had KC_NO in layers 2 and 3 assigned. (And originally, it had KC_F12 and KC_NO in layers 0 and 1 (or 1 and 0; can’t remember now) assigned.)

Try placing F12 on the F12 location in layer 2 and layer 3

I tried assigning Calc (KC_CALC) to the F12-key in layers 0 through 3, but it still behaves exactly the same. F12 opens the page, Fn+F12 does F12, and it swaps with Fn-Lock.

How it’s behaving puzzles me. It’s certainly not what it’s supposed to do.

I’d suggest saving your Via layout, then try clearing EEPROM / persistent memory. It seems occasionally Via can screw up something in its memory, which can cause glitches.

Saving or loading Via layouts (click to show)

The disk icon in the lower left takes you to the Save Current Layouts and Load Layout options

Clearing the EEPROM (click to show)

Resetting the keyboard to factory default / clearing persistent memory.
This will erase any and all changes you’ve made in Via (keyboard.frame.work).

Clearing EEPROM from Via.
If this is your first time using the site, you’ll have to authorize connection to your keyboard first.

1. Go to keyboard.frame.work.
2. Select a key to remap by clicking on it, the key will start to slowly flash
3. In the key selection area below, click on the Special section
4. Select the Any keycode, found at the bottom
5. Enter QK_CLEAR_EEPROM and press Confirm
6. On the keyboard, press the key you just remapped
7. Reload keyboard.frame.work for it to show the change

Alternately, clearing the EEPROM can be done from commandline using Framework’s qmk_hid tool github.com/FrameworkComputer/qmk_hid

You could also post your Via layout save file so I could see if any problem stands out there. It should show us the Via keymap more directly, without the potential for the webrowser interface to be presenting something wrong.