qmk/qmk_firmware

[Bug] TT(layer) cannot toggle

Open

#20,206 opened on Mar 21, 2023

View on GitHub
 (3 comments) (0 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

Describe the Bug

Setting TT(1) and TT(2). Momentary working fine. Toggle not functioning at all.

Relevant lines from config.h:

#define TAPPING_TOGGLE 2
#define TAPPING_TERM 200

I am on Arch Linux with avr-gcc 12.2.0-1 - I believe that might be relevant because of this closed issue. When I change OPT >= s to OPT >= 2 in qmk_firmware/builddefs/common_rules.mk, this issue is fixed but split keyboard functionality stops working.

Tagging @jypma and @kevinstadler who appear to have unresolved problems from the other, closed issue.

Any suggestions would be hugely appreciated!

Keyboard Used

redox

Link to product page (if applicable)

No response

Operating System

Arch Linux

qmk doctor Output

No response

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

Contributor guide

Research direction
Investigate the build script `builddefs/common rules.mk` to understand how the OPT variable is set and used. Determine why changing `OPT >= s` to `OPT >= 2` fixes the TT toggle issue but breaks split keyboard functionality. Look for differences in optimization level behavior between AVR and ARM architectures.
Tech stack
c
Domain
embedded iotbuild system
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.
Half day
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
CGitQMK build system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60