Files
Panama/config/dot/quickshell/services/IdleLock.qml
T
Gabriel Brown 2bc12e6022 Add wallpaper, power, date, accessibility, and real search
Continues the settings expansion toward replacing GNOME Settings for
everything Panama actually owns.

Wallpaper. A thumbnail grid rather than a path field: the value of this
setting is the picture, so typing a path to something you cannot see is
the worst version of it. Two things about hyprpaper 0.8 shaped this. Its
IPC is much smaller than older documentation suggests -- preload,
listloaded, unload, and reload all answer "invalid hyprpaper request",
so setting is a single call with no preload. And the "<empty>,<path>"
form that used to mean every output is silently ignored, so a wallpaper
set that way appears to succeed and never changes; outputs are walked
explicitly instead. hyprpaper.conf lives in the repo through the
~/.config/hypr symlink and so cannot hold machine state, which is why
the choice lives in the shared settings store and is re-applied at
startup.

Power & Lock. hypridle has no IPC for reconfiguration and its config is
hyprlang rather than the shared JSON, so scripts/panama-idle generates a
config from the settings store and restarts the daemon. The generated
file lives under XDG_STATE_HOME for the same symlink reason, with a
systemd drop-in pointing hypridle at it. Management is a real state and
the page says which one you are in rather than showing sliders that
quietly do nothing. Zero means never for all three timers, which a naive
template would render as "immediately".

Date & Time. Deliberately not stored in Panama's settings: the timezone
and network time belong to the machine and are shared with sessions that
never see this file. Storing a copy would create a second answer to a
question the system already answers. Reads and writes timedatectl
directly; a cancelled polkit prompt surfaces as an error rather than as
a value that appears to have been accepted.

Accessibility. Pointer size and text scale have to agree across three
consumers with no shared configuration -- the compositor, GTK, and the
shell -- so the store is the source of truth and the values are pushed
outward to gsettings and hyprctl setcursor.

Search now indexes the schema instead of the twelve page labels. "gaps",
"wallpaper", and "screenshot" previously found nothing on an app that
has all three, which is the clearest way a settings app feels smaller
than it is. Shortcuts are indexed by what they do. A contract asserts
every non-internal schema label is reachable, so a new setting cannot be
added in an undiscoverable state.

The GNOME delegation allow-list was widened to the panel names
gnome-control-center actually reports; the previous list contained
"users", which is not one of them and so opened nothing.

Claude-Session: https://claude.ai/code/session_01BRvzt4H8XXLPVH5MyYdk9L
2026-08-18 00:42:13 -04:00

116 lines
4.0 KiB
QML

pragma Singleton
// Idle, lock, and sleep timings.
//
// hypridle has no IPC for reconfiguration, and its config is hyprlang rather
// than the shared JSON, so this cannot work the way the compositor settings do.
// Instead scripts/panama-idle regenerates a config from the settings store and
// restarts the daemon.
//
// The generated file lives under XDG_STATE_HOME rather than ~/.config/hypr,
// because that directory is a symlink into the Panama repository -- writing
// there at runtime would put machine state into a tracked file. A systemd
// drop-in points hypridle at the generated path with `-c`.
//
// "Managed" is therefore a real state with two sides: when the drop-in is
// installed the timings below are in effect, and when it is not, hypridle is
// running the repository's shipped hypridle.conf and these values are only a
// stored intention. The Power page says which it is rather than showing
// controls that quietly do nothing.
import Quickshell
import Quickshell.Io
import QtQuick
import qs.config
Singleton {
id: root
readonly property string helperPath: Quickshell.shellDir + "/scripts/panama-idle"
property bool managed: false
property string serviceState: "unknown"
property string generatedPath: ""
property string lastError: ""
readonly property bool busy: statusQuery.running || applyRun.running
// The values as stored. They only describe what is running when `managed`.
readonly property int blankMinutes: DesktopPreferences.get("screenBlankMinutes")
readonly property int lockMinutes: DesktopPreferences.get("lockMinutes")
readonly property int suspendMinutes: DesktopPreferences.get("suspendMinutes")
readonly property bool lockOnSleep: DesktopPreferences.get("lockOnSleep")
// Blanking after locking is legal but pointless, and blanking with lock off
// is fine. Surfacing the one genuinely confusing combination beats silently
// reordering the user's numbers.
readonly property bool lockBeforeBlank: root.lockMinutes > 0
&& root.blankMinutes > 0
&& root.lockMinutes < root.blankMinutes
Process {
id: statusQuery
command: [root.helperPath, "status"]
stdout: StdioCollector {
onStreamFinished: {
try {
const state = JSON.parse(this.text);
root.managed = state.managed === true;
root.serviceState = String(state.active ?? "unknown");
root.generatedPath = String(state.generated ?? "");
root.lastError = "";
} catch (error) {
root.lastError = "Could not read the idle configuration.";
}
}
}
}
Process {
id: applyRun
onExited: (exitCode, exitStatus) => {
root.lastError = exitCode === 0 ? "" : "Could not update the idle configuration.";
root.refresh();
}
}
Component.onCompleted: root.refresh()
function refresh(): void {
if (!statusQuery.running)
statusQuery.running = true;
}
// Regenerates the config from the current settings and restarts hypridle if
// Panama is managing it. Safe to call when it is not: the file is written
// and nothing is restarted.
function apply(): void {
if (applyRun.running)
return;
applyRun.exec([root.helperPath, "apply"]);
}
function setManaged(enabled: bool): void {
if (applyRun.running)
return;
applyRun.exec([root.helperPath, enabled ? "install" : "remove"]);
}
// Regenerate whenever one of the four inputs changes. Coalesced, because a
// slider drag settles through several commits and each one would otherwise
// restart the daemon.
Connections {
target: DesktopPreferences
function onRevisionChanged(): void {
if (root.managed)
regenerate.restart();
}
}
Timer {
id: regenerate
interval: 400
onTriggered: root.apply()
}
}