From d5dff92682e4023629ece94480aec5c704634cad Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Thu, 2 Dec 2010 00:42:04 +0000 Subject: [PATCH] TODO.slip-multi-movfeat: plan for dealing with the double slip --- TODO.slip-multi-movfeat | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 TODO.slip-multi-movfeat diff --git a/TODO.slip-multi-movfeat b/TODO.slip-multi-movfeat new file mode 100644 index 0000000..da09b00 --- /dev/null +++ b/TODO.slip-multi-movfeat @@ -0,0 +1,20 @@ +* new section in ours.wiring for breaking up S0 S1 S2 S3 into + P0Q0V0R0 et al. + +* data2safety reads that and computes most things to have the + exploded version; the exception is layout-data.c SegPosCombInfo.pname + +* movpos.c needs to be modified to cope with mixed MovPosChanges + split MovPosChange into two structs, Change which is per-method + and MovPosChange which has a set of Changes one per relevant method + + Methods have to call a new change_done which is a bit like + motion_done but only does one Change and considers whether the + whole MovPosComb is done. + + evaluate should have a cost or a time or something rather than + just a count since wagglers are nearly free and points are not + and we always want to change a waggler rather than a point + +* There may be some fallout from the segment movfeat splitting + eg in the gui or gui plan displayer. -- 2.30.2