Fillter needs to be re-evaluated, when an downstream entity requests expandChildren() onto an upstream source. And obviously the ordering of the chained calls was wrong here. As it turns out, I had discovered that necessity to re-evaluate with the Transformer layer. There is a dedicated test case for that, but I cut short on verifying the filter in that situation as well, so that piece of broken copy-n-paste code went through undetected. This is in fact a rather esoteric corner case, because it is only triggered when the expandChildren() call is passed through the filter. When otoh the filter sits /after/ the entity generating the expandChildren() calls, everything works as intended. And the latter is the typical standard usage situation of an recursive evalutation algorithm: the filter is here used as final part to drive the evaluation ahead and pick the solutions. |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||