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
Issue: I'm using WPF with MaterialDesign in XAML, and I've encountered an issue with the Drawer component. Sometimes, the drawer MVVM does not display at all. However, when I modify the binding mode (e.g., set it to two-way binding) and trigger a hot reload, the drawer displays correctly.
I suspect this might be a UI refresh issue, but I'm unsure of the cause. The problem happens intermittently, and only the drawer component seems to be affected. Other parts of the UI are unaffected.
Has anyone experienced a similar issue, or could you provide insights on how to ensure the drawer reliably updates its state and displays correctly?
Version
4.5.0
The text was updated successfully, but these errors were encountered:
@q913777031 I can't reproduce your problem using the 4.5.0 version.
Can you share a repo showcasing this bug?
Alternatively, if that's an option, you can try to upgrade to the latest version. However, depending on how big your codebase is, this is a bit of work because there were some breaking changes in the 5.0.0 version.
For reference, here is the setup I have tried to reproduce your problem with:
MainWindow.xaml
Bug explanation
Issue: I'm using WPF with MaterialDesign in XAML, and I've encountered an issue with the Drawer component. Sometimes, the drawer MVVM does not display at all. However, when I modify the binding mode (e.g., set it to two-way binding) and trigger a hot reload, the drawer displays correctly.
I suspect this might be a UI refresh issue, but I'm unsure of the cause. The problem happens intermittently, and only the drawer component seems to be affected. Other parts of the UI are unaffected.
Has anyone experienced a similar issue, or could you provide insights on how to ensure the drawer reliably updates its state and displays correctly?
Version
4.5.0
The text was updated successfully, but these errors were encountered: