Skip to content
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 - No effects on item mouseover #66

Closed
Swiftpaws opened this issue Feb 13, 2020 · 1 comment · Fixed by #67
Closed

TreeView - No effects on item mouseover #66

Swiftpaws opened this issue Feb 13, 2020 · 1 comment · Fixed by #67
Assignees
Labels
bug Something isn't working
Milestone

Comments

@Swiftpaws
Copy link
Contributor

Describe the bug
When utilizing the treeview items on mouseover do not highlight correctly.
Tested with .net Core 3, .net core 3.1, .net 4.8 and .net 4.7.2

Somehow this is not the case in the demo application and I cannot wrap my head around why it works there and nowhere else. (Maybe because the view is a resource dictionary ?)

To Reproduce
I have created an example app with code taken from the demo application
https://github.com/Swiftpaws/AdonisTreeView-Mouseover

Expected behavior
Mouseover highlight (border)

@benruehl
Copy link
Owner

Thanks for reporting this.

This was a tough one. Although I fixed it now, I cannot tell you what is different in your demo app. Copying your MainWindow.xaml to AdonisUI.Demo resulted in a working TreeView so it was not about using a ResourceDictionary.

Anyway, explicitly writing {Binding Path=X instead of {Binding X in the style fixed it. This was not the first time this detail was important.

benruehl added a commit that referenced this issue Apr 11, 2020
Add the `Path` keyword explicitly to template bindings that target
attached properties because the missing keyword lead to bugs
in the past. See #18 and #66 for reference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants