aboutsummaryrefslogtreecommitdiffstats
path: root/desktop/modules/appearance/WallEngineModule.qml
AgeCommit message (Collapse)AuthorFilesLines
5 dayswallpaper engine: count down to the next changeDanilo M.1-2/+22
The header gave the clock time of the next change, which left the sum to the reader. It now counts down, from a one second timer that lives on the page, so nothing ticks while the page is closed. The engine still keeps only nextAt. The function is remaining(), not left(): left is Item's anchor line, so the call threw a TypeError and the status text went blank, which a clean hot reload does not show until the page is opened. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
13 dayswallpaper: engine page commits like the others, Start changes at onceDanilo M.1-0/+33
The page was the only settings page without the header's buttons, and it switched the engine from a checkbox beside the interval. Both looked like the engine had been started when it had not: - The minutes field saved on editingFinished, which needs Enter or a focus change. Clicking the checkbox takes neither, so a typed 1 was left at 30 and the first change was half an hour away. - Even at the right interval, the first change waited one full interval, so starting the engine did nothing visible. The interval and the two sources are now a draft in WallEngine, updated on every keystroke, and the header carries the state ("running, next change at hh:mm", "stopped", "unsaved changes") with Reset, Stop and Start, which reads Apply while running. Start commits the draft, sets the homes and changes the wallpapers straight away; Apply commits and restarts the timer. Hearts stay undrafted, written as clicked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
13 dayswallpaper: engine page glyphs as escapes, like the rest of the treeDanilo M.1-1/+1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
13 dayswallpaper: the engine's settings pageDanilo M.1-0/+36
A page for the wallpaper engine: the on switch, the interval in minutes, a Next button, and each screen's hearted list with a remove control and a dim for files the gallery's scan did not find. The module reads WallEngine.on itself, because a singleton is built on first use and the timer has to run from session start, page opened or not. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>