← Commit history

0.6.8: status window section now tells the problem story + shows the warning state (msedge screen-capture pinning the display)

John Lauer ·a63ccdf53f ·4mo ago ·parent 6d20777
4 files changed +11−5
README.md+9−3
@@ -89,10 +89,16 @@ A tiny always-on helper, **adom-stayawake.exe**, lives in your system tray. Righ  ![The Adom Screensaver system-tray menu, dark native Win32 menu](/blob/app/adom-screensaver/screenshots/systray-menu.png) -### The status / screen-locks window-The diagnostics screen. It runs with admin rights so it can read `powercfg /requests` and show, **live**, exactly what (if anything) is holding your display on, so the screensaver and display-off can't happen. Healthy state is green; if a screen-share, recording, or capture is pinning the display awake, it names the culprit and tells you how to stop it. Auto-refreshes every 10 seconds.+### The status window: catch what's secretly keeping your screen on+Here's a real problem it solves. A screen-share, a screen recording, a video call, or an Adom screen-capture left running quietly holds a Windows **display request** (`ES_DISPLAY_REQUIRED`). While that's held, Windows **won't turn your display off and won't start the screensaver**, so a bright screen can sit there burning in and wasting power all night, and nothing tells you which app to blame. (This bit us for several nights before the watchdog existed.) -![The Adom Screensaver status window showing keep-awake state and display-lock holders](/blob/app/adom-screensaver/screenshots/status-window.png)+The always-on helper runs with admin rights, reads `powercfg /requests` **live**, and tells you the truth, auto-refreshing every 10 seconds. When nothing is holding the display, it's green:++![The Adom Screensaver status window in the healthy green state](/blob/app/adom-screensaver/screenshots/status-window.png)++And when something is, it names the exact culprit and the one command to fix it (here, a Chrome/Edge **screen-capture** holding the display), and the tray icon flips to a warning so you actually notice:++![The Adom Screensaver status window warning that msedge is holding the display via screen capture](/blob/app/adom-screensaver/screenshots/status-window-warning.png)  ### The preferences window Reachable from Windows' Screen Saver **"Settings…"** button (or the tray), it reads your *actual* Windows power settings (lid, sleep, turn-the-display-off, lock) and shows them against the recommended "vibe-coding" profile, with one-click **Apply** for anything that's drifted. Fine-tune the idle timeout, how long the billboards play before the display turns off, and a never-turn-off (kiosk) option.
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "adom-screensaver",-  "version": "0.6.7",+  "version": "0.6.8",   "description": "Vibe-coding screensaver, fades up a live billboard of the latest Adom Wiki drops (truly cached to disk; plays webm silently, renders SVG) with a power-aware nerd-stats splash, while signed native keep-awake holds the machine so Claude Code + /remote-control threads survive. Win+Shift+L to launch.",   "type": "app",   "keywords": [
page.json+1−1
@@ -4,7 +4,7 @@   "slug": "adom-screensaver",   "title": "Adom Screensaver",   "brief": "Turn your laptop into an always-on vibe coding server: branded screensaver + native keep-awake (no PowerToys) + honest, hardware-aware power management.",-  "version": "0.6.7",+  "version": "0.6.8",   "install": {     "binary_name": "adom-screensaver",     "install_dir": "",
screenshots/status-window-warning.pngadded
⋯ 1 unchanged line ⋯