This is a list of proposed breaking changes for the 4.0.0 release. Feedback welcome!
C# 9 (Visual Studio 16.8) is now required to compile from source
*Nullable reference types are enabled *
Feel free to comment with any breaking changes you would like to request.
MaterialDesignFilledPasswordFieldPasswordBox to MaterialDesignFilledPasswordBox #2074 MaterialDesignOutlinedPasswordFieldPasswordBox to MaterialDesignOutlinedPasswordBox #2075MaterialDesignFilledTextFieldTextBox to MaterialDesignFilledTextBox #2076MaterialDesignOutlinedTextFieldTextBox to MaterialDesignOutlinedTextBox #2078HintAssist.FloatingOffset to be (0, -16) rather than (1, -16)PopupBox.PopupMode from MouseOverEager to ClickDialogClosingEventArgs constructor. #2079ValidationErrorColor to be MaterialDesignValidationErrorColor #2082DialogHost.DialogTheme to be InheritIcon and IconType in favor of PackIcon and PackIconKind #2079MaterialDesignColors.ColorManipulation.ColorHelper to ColorAssist #2083LargeArcConverter #2079ExpanderAssist members #2079TransitionAssist to root namespace #2081SecondaryAccentBrush and SecondaryAccentBrushColor #2080SecondaryAccentForegroundBrush and SecondaryAccentForegroundBrushColor #2080Vote for:
Rename ValidationErrorColor to be MaterialDesignValidationErrorColor
Change default behavior of DialogHost.DialogTheme to be Inherit
Remove Icon and IconType in favor of PackIcon and PackIconKind
Rename MaterialDesignColors.ColorManipulation.ColorHelper to ColorAssist
Hi @Keboo ,
I really like the new way the Resources are named in MahApps. It was quite a lot of work to get this done, but for the user it is much easier to remember the Keys IMO.
More info: https://mahapps.com/docs/guides/migration-to-v2.0#resource-keys
Just a suggestion, not a must have :-) .
Happy coding,
Tim
@timunie yea I have been following the MahApp theming changes and want to take a look at structuring it in a similar manner.
I think we should consider removing text field styles that only have an underline, with no fill or outline, i.e. MaterialDesignTextBox.
The reasoning for this is that they are no longer part of the spec. They were removed because research, conducted by Google, showed that users had trouble understanding that the line is an input field. It was often confused for a divider, and hint/label text was thought to be body text.
Here is a link to the article about the research:
https://medium.com/google-design/the-evolution-of-material-designs-text-fields-603688b3fe03
If people still want to keep the styles, I think we should at least change the defaults to filled.
@jizc I agree. I think the default should be changed to be the filled. There are not specific styles for the "not filled" (default) TextBox style that exists right now, since it is largely implemented with an attached property (TextFieldAssist.HasFilledTextField).
I think simply changing the default to be filled, but leave the attached property in place so if people really want the old look they can opt back into it by changing the attached property.
Most helpful comment
@timunie yea I have been following the MahApp theming changes and want to take a look at structuring it in a similar manner.