-
Notifications
You must be signed in to change notification settings - Fork 4.9k
.NET 10 P6 - WinForms #9951
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jamesmontemagno
wants to merge
2
commits into
dotnet10-p6
Choose a base branch
from
dotnet10-p6-winforms
base: dotnet10-p6
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
.NET 10 P6 - WinForms #9951
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
KlausLoeffelmann
approved these changes
Jun 27, 2025
Sorry, I missed this one. |
KlausLoeffelmann
requested changes
Jul 4, 2025
Something about the feature | ||
### Dark Mode & Styling | ||
|
||
This release brings several improvements to dark mode support in Windows Forms. ListView column headers, StatusStrip, ToolStrip, and buttons with FlatStyle 'Standard' now render correctly in dark mode, including fixes for color issues and regressions introduced in previous versions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
This release brings several improvements to dark mode support in Windows Forms. ListView column headers, StatusStrip, ToolStrip, and buttons with FlatStyle 'Standard' now render correctly in dark mode, including fixes for color issues and regressions introduced in previous versions. | |
This release brings several improvements to dark mode support in Windows Forms. | |
* `ListView` ColumnHeaders` are rendering correctly in dark mode now. | |
* All `ToolStrip` based controls (`MenuStrip`, `StatusStrip`) have their dedicated System Darkmode renderes, and do not rely any longer on additional Professional renderers, which make them compatible to certain A11Y requirements. | |
* All `ButtonBase` derived push-style controls have their dedicated dark mode renderers. Please note that in contrast to the existing docs, which was somewhat unprecise about the auto owner-rendering of using `ButtonRenderers` vs. wrapped Win32 Button controls, `Standard` `FlatStyle` renderers ARE owner drawn (and always were). Only setting the renderers to System actually wraps a `ButtonBase` control around the native Win32 Button and delegates painting/handling down completely. All remaining `FlatStyle` settings are either relying on VisualStyle-based- or entirely owner rendering. Thus, we've introduced a series of dedicated Button dark mode renderers which are also fixing a series of small bugs as well as one prominent bug, where Buttons would be ignoring dark mode background theming in 96 dpi. | |
* We fixed the base functionality as far as the Win32 allowed for `TabControl`: Horizontal orientation of tabs are rendering the tabs themselves now correctly in dark mode, and the oversized light-gray/white frame around the respective tab area has been mitigated for most scenarios. Note though that vertical tab orientation and different Tab-Button styles are NOT supported in dark mode, and are not at all high on our priority list. | |
* We fixed an issue with the `ListBox` dark mode, when using check boxes for List items which had been previously rendered with a white background. | |
* We've fixed a series of cases when both `RadioButton` and `CheckBox` controls had been rendered with a white background of the actual control background. |
|
||
### ScreenCaptureMode API | ||
|
||
New APIs have been introduced to exclude forms and controls from screen capture and a renaming of the ScreenCaptureMode API for clarity and consistency. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
New APIs have been introduced to exclude forms and controls from screen capture and a renaming of the ScreenCaptureMode API for clarity and consistency. | |
New security APIs have been introduced to protect forms containing sensitive information from the usual screen capture approaches. Please see the new `FormScreenCaptureMode` property for the `Form` class, and the `ScreenCaptureMode` settings for more information. | |
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.
Please update the release notes here as needed for Preview 6.