Flush clipboard history before quit#6
Open
sickn33 wants to merge 1 commit into
Open
Conversation
sickn33
force-pushed
the
flush-clipboard-history-saves
branch
2 times, most recently
from
17e6555 to
63e87ce
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ClipboardMonitor.flushPendingSave()to synchronously persist the latest in-memory historyapplicationWillTerminateWhy
Clipboard history saves are debounced by 0.5 seconds. If the app exits immediately after a history change, the pending
DispatchWorkItemmay never get a chance to write the latest state. This makes quit/terminate behavior deterministic without removing the debounce during normal use.Verification
git diff --checkxcodebuild test -project DropKit/DropKit.xcodeproj -scheme DropKit -destination 'platform=macOS' -derivedDataPath /private/tmp/dropkit-flush-derived CODE_SIGNING_ALLOWED=NOpassed 12 tests, 0 failures