You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the following in App.axaml fixes the issue for me:
...
<Style>
<Style.Resources>
<ResourceDictionary>
<!-- Fix bug with initialization of MaterialPaperBrush using MaterialThemeBase -->
<SolidColorBrushx:Key="MaterialPaperBrush"Color="#FF0000"></SolidColorBrush>
</ResourceDictionary>
</Style.Resources>
</Style>
<materialStyles:MaterialThemeBase />
...
I assume it was changed to avoid the awkward bug fix, which is a bug with Avalonia.DialogHost (pretty sure). We could always tackle the bug on their end?
Checklist
I have looked through existing issues to make sure that this bug has not been reported before
I have provided a descriptive title for this issue
I have made sure that this bug is reproducible on the latest version of the application
I have provided all the information needed to reproduce this bug as efficiently as possible
I have sponsored this project
The text was updated successfully, but these errors were encountered:
I understand that, but I found that MaterialThemeBase works extremely poorly and there were too many issues I've experienced in the projects where I tried to use it. In general, the Material tooling seems to be very buggy when it comes to Avalonia.
After some consideration, I decided that using MaterialTheme was the least of all available evils.
The flash still seems to happen even when using MaterialThemeBase, it just goes from black (colors unset) to dark instead of light to dark. It's more noticeable if your configured theme is set to light instead of dark, in that case.
The flash still seems to happen even when using MaterialThemeBase, it just goes from black (colors unset) to dark instead of light to dark. It's more noticeable if your configured theme is set to light instead of dark, in that case.
Interesting, I see that now -- This happens with my proposed fix, but not in my original PR code. Not sure where the bug is, then.
Going to close this as "won't fix" as this is pretty insignificant in the grand scheme of things, and I want to avoid dealing with the intricacies of Material.Avalonia as much as possible 😅
Version
v2.5
Platform
Windows 10
Steps to reproduce
Details
A fairly minor cosmetic issue, but I believe it was introduced in 03218e8. The reason is that
MaterialTheme
is not meant to be overridden from code with theCurrentTheme
property --MaterialThemeBase
is for that purpose.Using the following in
App.axaml
fixes the issue for me:I assume it was changed to avoid the awkward bug fix, which is a bug with Avalonia.DialogHost (pretty sure). We could always tackle the bug on their end?
Checklist
The text was updated successfully, but these errors were encountered: