-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
TreeView nodes don't expand #144
Comments
I hit this problem as well on Windows 11. Using a local build of UraniumUI instead of the nuget packages fixed the issue for me. My guess is that it was fixed by #109 |
@LycianSeattle PR #109 was merged into 2.1 but the bug is still reproduced in 2.1.0 NuGet package. |
🤷 idk when the fix happened then. I do know locally referencing the projects instead of NuGet packages worked for me. That was the biggest churn I saw. |
It might be related to If the node binding context (nodes in viewmodel) doesn't have a property named I'll investigate it |
You're right, ButtonView has issues on windows in release mode. |
Can you try the new HotFix version |
@enisn yep 2.1.1 fixed expand handling, but there is a new bug now: nodes with no children show expand button, while shouldn't. UPD: Ah, sorry, it was me trying to fix |
Can confirm 2.1.1 fixed the issue for me too. Thanks for the quick turnaround! |
Steps to repro:
I just created a new app from the 'Uranium UI MAUI Blank Template'; added
<material:TreeView ItemsSource="{Binding Nodes}"/>
to the main page; and defined the nodes by copying the 'MyItems' class and Nodes initialization code from the examples in the docs: https://enisn-projects.io/docs/en/uranium/latest/themes/material/components/TreeViewExpected Results:
You can expand the node and see the children.
Actual Results:
I can see a hover state over the chevron for a given node, but when I click it doesn't expand. No error is thrown either it just does nothing.
My sample app to repro: https://github.com/Felicity-R/UraniumTreeViewTest
Tested on Windows 10, 19043.2251
The text was updated successfully, but these errors were encountered: