Fix: Prevent multiple settings windows from opening#11
Closed
nek0der wants to merge 1 commit into
Closed
Conversation
- Check App.Windows for existing SettingsWindow before creating new one - Use LINQ FirstOrDefault to find open settings window - Activate existing window instead of creating duplicate - Remove need for instance field and event handler cleanup - Follow single source of truth pattern with App.Windows collection
|
This pull request has been automatically marked as stale because it has not had recent activity. |
|
This pull request has been automatically closed due to inactivity. |
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.
Description
Fixes a bug where clicking the Settings button multiple times would open multiple instances of the settings window, instead of activating the existing one.
Implementation:
App.Windows.OfType<SettingsWindow>().FirstOrDefault()to check for existing windowApp.WindowscollectionBenefits:
Related Issue
N/A
Type of Change
How Has This Been Tested?
Test Configuration:
Manual Test Steps:
Unit Tests:
Screenshots (if applicable)
N/A - Behavior fix, no visual changes
Checklist
Breaking Changes
N/A
Additional Notes
Files changed:
MainWindow.xaml.cs- Added window existence check before creating new SettingsWindowTechnical details:
using System.Linq;for LINQ operationsApp.Windowscollection managed bySettingsWindow.ClosedeventThis follows WinUI/WPF best practices for managing multiple window instances.