Ticket #139 (closed enhancement: fixed)
Reordering of child nodes
| Reported by: | paulweiss@… | Owned by: | |
|---|---|---|---|
| Priority: | low: annoyance, enhancement | Milestone: | 2.0 |
| Component: | Version: | 1.10 | |
| Keywords: | Cc: |
Description
I can provide a straight-forward example: Suppose Glen makes a graph for himself, where the tool first defines three nodes, then the edges between them. I'm not so good at hand-generating long hex UIDs, so I'll use the labels as the node identifiers.
allThatStandsBetweenMeAndWorldMastery -> orderPreservingTrees
allThatStandsBetweenMeAndWorldMastery -> implementingUndoAndRevertAndImmutable
but then, because of the frequency and amplitude of the anguished howls of his users, he decides to flip the implementation order of the last two nodes; he certainly does not want the layout algorithm to cause him to commit to the definition order simply because there's no convenient way to reorder the child nodes. (The domain of the example is just joking around, I hope obviously.) [paulweiss]