Ichthyostega
f84517547b
- had to fix a logical inconsistency in the underlying Expander implementation in TreeExplorer: the source-pipeline was pulled in advance on expansion, in order to "consume" the expanded element immediately; now we retain this element (actually inaccessible) until all of the immediate children are consumed; thus the (visible) state of the PipeFrameTick stays at the frame number corresponding to the top-level frame Job, while possibly expanding a complete tree of flexible prerequisites This test now gives a nice visualisation of the interconnected states in the Job-Planning pipeline. This can be quite complex, yet I still think that this semi-functional approach with a stateful pipeline and expand functors is the cleanest way to handle this while encapsulating all details |
||
|---|---|---|
| .. | ||
| application | ||
| steam | ||
| vault | ||
| DIR_INFO | ||