From 72b3f10a8a7239b26a945fcd44daef0b6a301722 Mon Sep 17 00:00:00 2001 From: Iisyourdad Date: Thu, 11 Jun 2026 11:48:09 -0500 Subject: [PATCH] Fixed a bug where a resumed recording wouldn't update the image --- app/capture.js | 8 ++++++++ docs/CHANGELOG.md | 4 ++++ 2 files changed, 12 insertions(+) diff --git a/app/capture.js b/app/capture.js index dcd5821..7100f02 100644 --- a/app/capture.js +++ b/app/capture.js @@ -201,6 +201,14 @@ class CaptureService { }; if (this.hiddenForSession && win && !win.isDestroyed()) setTimeout(arm, 400); else arm(); + } else if (!wasPaused && this.session.paused) { + // Pausing stops the background cache refresh loop, but it does so by + // returning early (see startClickCaptureCache's refresh) without + // resetting captureCacheRunning or clearing captureCache. Without this + // call, resuming would find captureCacheRunning still true, so + // startClickCaptureCache() would no-op and every click afterwards + // would reuse the stale pre-pause frame instead of a fresh one. + this.stopClickCaptureCache(); } if (this.rebuildTrayMenu) this.rebuildTrayMenu(); this.notify('capture:state', this.state()); diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md index c75ef1e..b2369c7 100644 --- a/docs/CHANGELOG.md +++ b/docs/CHANGELOG.md @@ -92,6 +92,10 @@ Initial release. literal text "undefined" by an old bug); a corrupted file is now treated as empty instead of crashing the dialog, and is overwritten with valid JSON the next time settings are saved. +- Resuming a paused capture session no longer reuses the same stale + background screenshot for every click capture (only the click marker + moved); pausing now fully resets the click-capture cache so resuming + starts a fresh background refresh loop. ### Added (initial feature set)