Conversation
MiMoHo
force-pushed
the
preserve-clipboard-on-launch
branch
from
September 9, 2026 15:22
05531d3 to
fea2844
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
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
awakeFromNib.changeCountinstead.Root cause
declareTypes:owner:creates new pasteboard contents. Calling it on the general pasteboard during launch therefore replaced the clipboard before Flycut had observed it.Verification
origin/masterand passes with this change:python3 Tests/ClipboardLaunchRegressionTests.py726553ecf7bc9a566310a528b0ccdf24efa0fc9bf14c78544eb9b2487cfa4fb4before and after review.origin/masterand this branch linked the same 20 PBX source files into native arm64 Mach-O executables with 0 errors and the same 40 existing compiler warnings.Scope and remaining verification
This PR only preserves clipboard contents at launch. It does not include the clipboard-content logging removal already submitted in #5, and it does not change clipping selection or synthetic paste event posting.
The visible
Shift+Command+Vend-to-end path still needs to be repeated on the final, non-beta macOS 27 release with Accessibility access granted to the exact tested app. That separate OS-compatibility check is not claimed as passed here.