From d4996abb0f75657f877a858a93afdd1eb9763bd9 Mon Sep 17 00:00:00 2001 From: "Danilo M." Date: Wed, 7 Oct 2026 18:36:20 +0200 Subject: docs(spec): island flag follows whichever keyboard is main The same keyboard appears as a different device over USB and over its dongle, so the main device is resolved per event, never cached. Co-Authored-By: Claude Opus 5.5 --- docs/superpowers/specs/2026-10-07-island-core-design.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'docs/superpowers') diff --git a/docs/superpowers/specs/2026-10-07-island-core-design.md b/docs/superpowers/specs/2026-10-07-island-core-design.md index 79828ce..93af743 100644 --- a/docs/superpowers/specs/2026-10-07-island-core-design.md +++ b/docs/superpowers/specs/2026-10-07-island-core-design.md @@ -164,7 +164,10 @@ StatusNotifier host. `hyprctl switchxkblayout next|prev`; click does nothing. The current layout comes from Hyprland's `activelayout` event rather than a 2s poll. The keyboard is the one Hyprland marks `main`, not a hardcoded device name, which -`wb-lang` used. +`wb-lang` used and which broke when the same keyboard moved from its 2.4GHz +dongle to USB. The main keyboard is resolved again on each switch and on +`activelayout`, never cached, because plugging the other connection changes +which device is main. ## Removing waybar -- cgit v1.2.3