Win32 UI #3
Merged
Win32 UI #3
Conversation
This file contains 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
…dow is searching for.
…tification once per thread, instead of once per file.
…t it doesn't call into destroyed explorer window.
… derived one that additionally selects objects on it.
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.
This PR adds a new UI implementation written in pure Win32 API.
• The app now uses significantly less memory for display UI (81 MB -> 2 MB for the search window, 89 MB -> 4.5 MB for an empty search results window, 183 MB -> 96 MB with for a search results window with 36243 results in it).
• Much more native look on Windows 11;
• Proper high DPI support;
• Faster startup time.
WPF version will still be available for now.