Skip to content

fix: preserve recent captures across saves and editor handoffs - #134

Merged
jondkinney merged 1 commit into
omacom:mainfrom
tusharmalpani20:fix/recent-snapshot-persistence
Sep 21, 2026
Merged

jondkinney merged 1 commit into
omacom:mainfrom
tusharmalpani20:fix/recent-snapshot-persistence

Conversation

@tusharmalpani20

Copy link
Copy Markdown
Contributor

Recent captures can lose edits or reference the wrong working document when autosave, output, reopening, and editor handoffs overlap.

Publish recent entries only after their source image and operation log are ready. Preserve the existing document when publication fails and remove a replaced entry only after its replacement succeeds.

Also:

  • Prevent stale autosave results from replacing the current document's source.
  • Preserve original pixels so reopening does not apply cuts twice.
  • Finish pending document writes safely during shutdown.
  • Preserve recent-entry identity through window-selection handoffs.
  • Open recent captures for editing from the initial capture screen.
  • Prevent output from racing unfinished edits.

Keep persistence work off the UI thread.

Validation:

  • Full headless smoke suite and affected clang-tidy checks passed.
  • Covered publication failure and retry, stale autosaves, reopening, full-shelf replacement, shutdown, and valid and invalid handoffs.

@jondkinney
jondkinney force-pushed the fix/recent-snapshot-persistence branch from 43c8026 to a37f56c Compare September 21, 2026 19:52
@jondkinney
jondkinney merged commit 83bc977 into omacom:main Sep 21, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants