fix(windows): prevent Settings from auto-opening on launch#1022
Merged
fix(windows): prevent Settings from auto-opening on launch#1022
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
Settings { ... }was the first scene invar body: some Scene, and SwiftUI on macOS 14/15 auto-launches the first declared scene even when it's aSettingsscene — contrary to documentation. Compounding this,.background(SettingsNotificationBridge())read@Environment(\.openSettings)from inside the Settings scene, which forced the scene to materialize duringNSApplicationMainapplicationDidFinishLaunchingenter, the only window present wascom_apple_SwiftUI_Settings_windowopened by SwiftUI's runApp before user code ranFix
Window("Welcome", ...)first (default-launches),Settings { ... }lastWindowOpener.shared.openSettings(tab:)— wired via the existingWindowOpenerBridgeinside the Welcome scene using\.openSettings.openSettingsWindownotification round-trip andSettingsNotificationBridge; collapse 3 callsites onto the singleWindowOpener.shared.openSettings(tab:)callWindowChromeConfiguratorfrom an asyncTask(which ran after window creation) to a synchronousviewDidMoveToWindowhook on a privateChromeHostViewsubclass —isRestorable = falsenow lands before AppKit can encode restoration state, and the configurator is symmetric (togglingfullScreenableback on now removes.fullScreenNone)Test plan
.tablepluginon Finder → installs and opens Settings on plugins tab