2 * movpos.c needs to be modified to cope with mixed MovPosChanges
3 split MovPosChange into two structs, Change which is per-method
4 and MovPosChange which has a set of Changes one per relevant method
6 Methods have to call a new change_done which is a bit like
7 motion_done but only does one Change and considers whether the
8 whole MovPosComb is done.
10 evaluate should have a cost or a time or something rather than
11 just a count since wagglers are nearly free and points are not
12 and we always want to change a waggler rather than a point
14 * There may be some fallout from the segment movfeat splitting
15 eg in the gui or gui plan displayer.