I just finished a build of the ScottoFrog and was attempting to use it on a Mac. This worked fine everywhere but the terminal. In terminal it was sending two weird characters that came out as: 0xef9cb9 0xef9cb9 (Well the symbols those unicode bytes represent) everytime I hit the symbol toggle key.
In the QMK key tester, the pressing symbol would send the clear key which appears to be in the num-lock position on the displayed keyboard pattern.
(Green box)
Based on that, I checked the firmware and discovered
|
// Force num lock always on |
|
bool led_update_user(led_t state) { |
|
if (!state.num_lock) { |
|
tap_code(KC_NUM_LOCK); |
|
} |
|
return true; |
|
} |
// Force num lock always on
bool led_update_user(led_t state) {
if (!state.num_lock) {
tap_code(KC_NUM_LOCK);
}
return true;
}
For whatever reason, that appears to be what tripped it up. Removing that bit of code fixes the errant behavior in terminal. This might be a gotcha for other Mac users.
I just finished a build of the ScottoFrog and was attempting to use it on a Mac. This worked fine everywhere but the terminal. In terminal it was sending two weird characters that came out as:
0xef9cb9 0xef9cb9(Well the symbols those unicode bytes represent) everytime I hit thesymboltoggle key.In the QMK key tester, the pressing
symbolwould send theclearkey which appears to be in the num-lock position on the displayed keyboard pattern.(Green box)
Based on that, I checked the firmware and discovered
scottokeebs/ScottoFrog/PCB/QMK/custom_keys.c
Lines 3 to 9 in b6a4394
For whatever reason, that appears to be what tripped it up. Removing that bit of code fixes the errant behavior in terminal. This might be a gotcha for other Mac users.