Hi @Erel
I did a bit of search to try to figure out why this BUG exists, and if it has been resolved in newer Java Versions, and it seems to have been.
Furthermore, my readings .... ... lead me to think that the solution may reside on the UpdateItem method, which could be used inside the TableTreeItem_ExpandedChanged(Expanded As Boolean), but for it to be usefull, it needs to also provide a reference to the item that changed its expanded status....
SOooooo... maybe a correction with the upcoming B4J v10.0?
I did a bit of search to try to figure out why this BUG exists, and if it has been resolved in newer Java Versions, and it seems to have been.
Furthermore, my readings .... ... lead me to think that the solution may reside on the UpdateItem method, which could be used inside the TableTreeItem_ExpandedChanged(Expanded As Boolean), but for it to be usefull, it needs to also provide a reference to the item that changed its expanded status....
SOooooo... maybe a correction with the upcoming B4J v10.0?