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
Encountered multiple binding failures in XAML when ProgressBar is styled with MaterialDesignCircularProgressBar. There was no binding failures previously in v5.1.0 and it appears only after I upgraded it to the latest v5.2.1.
Uncomment <Window.Resources> in MainWindow.xaml for the workaround
Workaround
I'm currently overriding the style in Resources by reverting it back to the style in v5.1.0.
I believe this bug was introduced when the global converter was converted to instance. StaticResource to x:Static
I did some research, seems like a x:Static instance converter doesn't work well with ElementName binding because it has no access to the visual tree? (shrug)
Please consider reverting this style to use StaticResource converter until there is a fix
Version
v5.2.1
The text was updated successfully, but these errors were encountered:
As mentioned in this stackoverflow post, adding a x:Name to the PathFigure and ArcSegment somehow solves this problem. I have no idea why.
The changes would be made in the following 2 lines:
Because I don't understand the "fix" mentioned above, I am not (yet) going to open a PR. Maybe we can find a different, more viable solution.
Update
While applying an x:Name fixes this particular issue, I don't think this is the correct fix.
The problem that is reported here is a general problem with the static referenced converters which was implemented in #3732.
We probably have this issue all throughout the library (e.g. see #3834)
I noticed it again today: this bug does not break apps itself, but it sure is annoying for the devs to sort out the errors when you are instead hunting for binding errors in your app.
Bug explanation
Problem
Encountered multiple binding failures in XAML when ProgressBar is styled with MaterialDesignCircularProgressBar. There was no binding failures previously in v5.1.0 and it appears only after I upgraded it to the latest v5.2.1.
Steps
Code
<Window.Resources>
inMainWindow.xaml
for the workaroundWorkaround
StaticResource
tox:Static
x:Static
instance converter doesn't work well withElementName
binding because it has no access to the visual tree? (shrug)StaticResource
converter until there is a fixVersion
v5.2.1
The text was updated successfully, but these errors were encountered: