qmk/qmk_firmware

[Bug] KC_RALT sending wrong key event?

Open

#15,823 opened on Jan 10, 2022

View on GitHub
 (3 comments) (3 reactions) (0 assignees)C (43,867 forks)batch import
bughelp wanted

Repository metrics

Stars
 (20,368 stars)
PR merge metrics
 (Avg merge 20d 9h) (27 merged PRs in 30d)

Description

Hi, and thanks for this awesome piece of software. I encountered some weird behavior with the ALTGR key and the Eurkey layout and couldn't find anyone mentioning this online. So far I have been using a plain old qwerty keyboard and when hitting ALT GR on that one the QMK Configurator Testing function gives me:

KEY-DOWN - QMK: KC_RALT Event key: AltGraph    Code: AltRight      KeyCode: 225
KEY-UP   - QMK: KC_RALT Event key: AltGraph    Code: AltRight      KeyCode: 225 in 83.000ms

on my redox I am getting this.

KEY-DOWN - QMK: KC_RALT Event key: Alt         Code: AltRight      KeyCode: 18
KEY-UP   - QMK: KC_RALT Event key: Alt         Code: AltRight      KeyCode: 18 in 85.000ms

So it seems the sent keycode is actually not correct. This wouldn't really bother me but sadly enough the Alt Gr key is the modifier key for the EurKey layout to access Umlauts. Any help would be greatly appreciated. Cheers!

  • keyboard: redox/rev1 with some minor keymap tweaks
  • Operating system: Manjaro (5.13.19-2-MANJARO)
  • AVR GCC version: 8.3.0
  • ARM GCC version: 11.2.0
  • QMK Firmware version: 0.15.2

Contributor guide

Research direction
Investigate the different keycodes sent for KC RALT on different keyboards. Examine QMK's handling of KC RALT and the Eurkey layout. Compare the implementation on the redox vs. a standard QWERTY keyboard to identify the source of the differing keycode.
Tech stack
c
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitCQMK basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40