-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Initially tree is expanded but isExpanded() is set to false leading to a minor bug #17
Comments
@DrHowdyDoo Thank you for reporting i will check and fix it |
Hello @DrHowdyDoo, I am trying to reproduce it with FileTreeFragment example using treeViewAdapter.expandNode(javaDirectory); Can you please write simple code to reproduce it or write instruction to used it in FileTreeFragment |
I am not using any |
I know i mean we need to create snippet of code to reproduce tge issue |
can you see it in my github project ?? it's in progress and i am facing couple of bugs in the treeview. |
Good i will check it and fix them |
@DrHowdyDoo Your idea is cool i installed the app but i clicked on many apps components and the app show no tree or info. Any tips on how to use it to debug the issue Thanks |
You have to set the app as digtal assistant and then invoke it like you do with google assistant to make it work. |
if it does not show anything remove it as your digital assistant and then set it again |
It's not working on my real device, i will try emulator |
Try installing the apk from the repo releases section. i have put layout_inspector_v1.0 apk there. |
Describe the bug
When the tree is shown for the first time, it is all expanded but the treeNode class has a false set in isExpanded variable, because of this when you tap on the node it expands again replicating it's childrens.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Either the tree should be collapsed from the start or isExpanded should be set to true.
Screenshots
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: