good news: it (almost) works out-of-the-box as expected. There is only one problem: expandChildren() alters the content of the data source, yet downstream decorators aren't aware of that fact and continue to present cached evaluations, until the next iterate() call is issued. Yet unfortunately this iterate already consumes the first of the expanded children, which thus gets shadowed by the cached outcome of parent node already consumed and expanded at that point See the first example: "10-8-expand-8-4-2-6-4-2" should be 6 ^^^ |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||