Possible bug?

[busslina]

tree-error.webm

[jawwad-hassan89]

Is this related to this PR-28?
I will look into this.

[busslina]

Is this related to this PR-28? I will look into this.

Not really. The thing here is that when I switch tabs, state get disposed. When re-enter on the tree tab I tried to reuse the Tree object. The root node is okay (gets reset to collapsed, but the remaining nodes that were previously get expanded, now are collapsed but its state say are expanded (you can see the ChevronIndicator), so I must click twice on it to get well expanded.

I bypass this bug(?) by creating my own paralel Tree which save the expanded state and the children values. So when I re-enter on the Tree tab, I create a new Tree (your Tree) and re-install the state saved on my tree.

[StoneColdRepins]

@busslina can you elaborate on your solution to bypass the bug(?) or post a code sippet

[busslina]

I just simply have a parallel tree in which I save the state. When I revisit this tab, I recreate the node states based on this parallel tree.

Seems that your node implementation is not prepared for a scenario where the page/container gets disposed and rebuilt again. They save the expanded state. But when they get recreated, they are not expanded but still have the expanded state.

I could pass my code, but it is just a patch. I recommend you to review your code and when the tree is re/build check the nodes and expand them if they are marked as exoanded

[StoneColdRepins]

hi please send the patch, i am new to flutter and using the control in my app

[busslina]

hi please send the patch, i am new to flutter and using the control in my app

https://gist.github.com/busslina/e60a41ceca418151c491a730f12a57b0

If you want help to understand my code, ask me in the Gist