Add Windows 11 compatibility declarations and fix absolute path crash #346
Conversation
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
1 participant
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.
Changes:
Windows 11 Compatibility: Added a proper app.manifest declaring support for Windows 10/11 GUIDs {8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a} to ensure correct OS behavior (e.g., taskbar grouping, corner rounding).
Critical Bug Fix: Resolved a System.ArgumentException when saving groups. The issue was caused by the application using relative paths, which failed if the working directory changed. The logic in
Category.cs has been refactored to use strict absolute paths derived from the executable's location.
Documentation: Updated README.md to explicitly state support for Windows 10 & 11.