turns out that -- again -- we miss some kind of refresh after expanding children. But this case is more tricky; it indicates a design mismatch in IterSource: we (ab)use the pos-pointer to communicate iteration state. While this might be a clever trick for iterating a real container, it is more than dangerous when applied to an opaque source state as in this case. After expanding children, the pos-pointer still points into the cache buffer of the last transformer. In fact, we miss an actualisation call, but the IterSource interface does not support such a call (since it tries to get away with state hidden in the pos pointer) |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||