Distillation

Date: Jul 14, 2026

• 🟡 (01:41) User suggested allowing timing tweaks with special keys in adjust layer.
• 🟡 (01:41) Assistant explained ZMK limitations: hold-tap parameters are compile-time constants.
• 🔴 (01:41) User's idea for timing tweak keys is not possible without patching ZMK's C source.
• 🟡 (01:42) Assistant proposed alternative: compiling multiple presets and switching between them live with keys.
• 🟡 (01:42) Assistant outlined costs: coarse tuning, complexity, bigger firmware.
• 🔴 (01:44) User asked if timings can be read from a region like keymaps in ZMK Studio.
• 🟡 (01:44) Assistant explained keymaps are runtime-mutable by design, but hold-tap timings are not.
• 🔴 (01:45) Hold-tap timings are stored as const values in devicetree config struct.
• 🟡 (01:46) Assistant described required changes to make timings settings-backed: add struct, change driver, add behaviors.
• 🟡 (01:47) Assistant suggested realistic middle ground: switching between presets or behaviors.
• 🟡 (01:47) Assistant offered to help scope ZMK core changes if user wants to implement timing settings.
• 🟡 (01:47) Assistant asked if user wants to add named #defines for timing values for easier future tweaks.