Put power profiles and the colour scheme in the Control Center

The panel is for "change it now" decisions, and two of the most obvious were reachable only through Settings. Night Light was already here; these were the genuine gaps. The colour scheme is a grid toggle beside it. It writes the preference and stops -- ColorScheme propagates the change to GTK, the portal, the terminals, the launcher, btop, tmux and the lock screen, and nothing in the panel needs to know that list. Light is the lit state because dark is what Panama ships, and "active" reads as the non-default everywhere else in this grid. Power profiles are a summary row that expands into a list, matching how the audio device lists behave. A row per profile rather than a cycling button: there are three, and cycling passes through one you did not want on a machine where the change is immediate and audible. The row hides entirely where no power-profiles daemon is running, and the panel re-reads the active profile on open, because the daemon owns it and anything on the system can change it. Worth recording, because it invalidates something I believed earlier in this session: the live shell runs `quickshell --daemonize` and does NOT hot-reload. Editing a file under config/dot/quickshell changes nothing until the shell is restarted. The PID changes I had taken for hot reloads were tests killing and restarting it. Both of these controls were written, verified in a harness, and completely absent from the running panel until the shell was restarted. Claude-Session: https://claude.ai/code/session_01BRvzt4H8XXLPVH5MyYdk9L
2026-08-18 16:25:59 -04:00
parent 63f4bdb547
commit bd5d030d91
4 changed files with 108 additions and 0 deletions
@@ -0,0 +1,57 @@
+// The three system power profiles, as an expandable list.
+//
+// A row per profile rather than a cycling button: there are three, and cycling
+// through them means passing through one you did not want on a machine where
+// the change is immediate and audible. The same shape the audio device lists
+// use, so the panel reads consistently.
+//
+// The daemon owns the profile -- it survives a shell restart and anything else
+// on the system can change it -- so this reads back rather than assuming, the
+// same as monitor brightness.
+
+import QtQuick
+import qs.config
+import qs.services
+
+Column {
+    id: root
+
+    spacing: 2
+
+    Repeater {
+        model: PowerProfiles.profiles
+
+        RowButton {
+            required property var modelData
+
+            width: root.width
+            icon: {
+                switch (modelData) {
+                case "power-saver": return "power-profile-power-saver-symbolic";
+                case "performance": return "power-profile-performance-symbolic";
+                default: return "power-profile-balanced-symbolic";
+                }
+            }
+            iconFallback: "preferences-system-power-symbolic"
+            label: PowerProfiles.label(modelData)
+            sublabel: PowerProfiles.detail(modelData)
+            selected: modelData === PowerProfiles.active
+            dimmed: PowerProfiles.busy
+            onClicked: PowerProfiles.set(modelData)
+        }
+    }
+
+    // Only when it is true. A machine that cannot deliver the profile it is set
+    // to is the one case where the label alone is misleading.
+    Text {
+        visible: PowerProfiles.degraded !== ""
+        width: root.width
+        text: "Limited right now: " + PowerProfiles.degraded
+        color: Theme.fgMuted
+        font.family: Theme.fontFamily
+        font.pixelSize: Theme.fontSizeSmall
+        wrapMode: Text.WordWrap
+        leftPadding: 10
+        topPadding: 4
+    }
+}