I guess we should explain why in this case Sequence operator doesn't work as you expected:
Sequencer uses internally a counter to define the index of next item. This index is incremented only when node is evaluated.
Lets see this example with three Sequence nodes (AB, AC, AB-AC).
- Segment 1) SeqAB_AC is evaluated, its initial index is 1, so it takes the first input (SeqAB). Same for SeqAB which returns A. The indexes of SeqAB_AC and SeqAB are incremented (set to 2)
- Segment 2) SeqAB_AC is and evaluated. Since its index is 2, it takes the second input (SeqAC, index = 1), which returns A. The index of SeqAB_AC is incremented and reset to 1, and SeqAC index is set to 2.
- Segment 3) SeqAB_AC (index = 1) returns SeqAB again, which once evaluated ( index 2) returns B. Both indexes are incremented.
- Segment 4) SeqAB_AC (index = 2) returns SeqAC, and this returns C.
So the final sequence is AABC, not ABAC.
Instead, Compose operator seems similar but works completely different. All input segments are chained together and handled as an unique Segment.
For example, when used as Corner or Evenly, Compose returns multiple sub-segments, but Sequence only one.
Sequence operator allows to modify its internal index (i.e. exporting it as a parameter), but Compose not.
I hope everything is clear now. If not, please don't hesitate to ask.