Survex To-Do List

Bugs

This gives "*** Singular!!!" warning with DEBUG_INVALID on:
```
1 2 50000 0 -
1 2 5 0 -30
```
aven: loading a .3d file with no survey data (or which has a valid header but is broken later) with a survey already loaded doesn't work well.
img.c: eliminate duplicate img_LABELs when reading .PLT files.

by default put crosses on those points with no legs attached (unused fixed points)?
label junctions/dead ends?
colour by traverse
section colouring/selective labelling
clipping - want to select a clip sphere (or maybe cube) centred on centre on rotation I think.
colour by cave (and more generally by sub-prefix): "aven --survey 161 --colour-by-sub-prefix all.3d" would result in lhroute, rhroute, adrian, etc all getting different colours...
check on monochrome displays - especially that depth colouring looks OK
Feed back redraw time to key based movement as in caverot? Or perhaps best not to? It depends on whether we expect people to hold down keys or not... Perhaps something smart where the first press is a fixed size, then after that it depends on the redraw?
Some way to display all the names of an equated station (e.g. in pop-up window or the info panel).
Highlight a whole survey by clicking on it in the tree...
aven for MSDOS?

Check skip blank pages works (checked printps)...
printdm: put standard scaling in print.ini for canon bj (work out what's up with vertical size...)

Platform specific versions of docs?
Put more terms in terminology in docs ? trip, instrument, ...
Finish off manual loose ends.
Look at using docbook2man instead of docbook-to-man (command is nsgmls man_aven.sgml | sgmlspl /usr/lib/perl5/sgmlspl-specs/docbook2man-spec.pl)
Make sure there's documentation for all the various settings in print.ini (colours aren't documented at present)

flag legs as "skeletal" or something? (i.e. not in the cave passage) - e.g. a radiolocation leg from one passage to another isn't surface, but it isn't in the cave itself either (it's through rock). You could just call it surface but maybe later we want to use the surface flag to produce points for a surface triangulation...
?outlaw prefixes on stations in data legs (as Todd has lobbied for) and then the prefix of a leg == prefix of each end...?
comma separated dates in *date?
Find a solution to Thilo's "." problem.
LRUD?
multiple readings - perhaps like so:
```
*calibrate compass {000.5 001.0 001.25}
1 2 10.23 {000 001} -02
2 3 {10.16 10.17} 127 {+06 +05}
3 4 11.98 007 {+03 +03}
```
Also, should we add "*set bra {", "*set ket }" or similar? Or is *set kind of deprecated? Implement as extension to number format? Then we can easily allow any suitable numeric value to be repeated, but bear in mind that bearings don't average like normal numbers...

extract help screen from caverot.c for translation
quotes in messages - translate too? e.g. `XXX' to Ť XXX ť. Eric suggests not in French.
extract --help messages for translation.
control of output units in .err file and in stats at end of cavern run? In fact anywhere we report a value in degrees or metres, the units should be selectable

resolve entries in TODO; resolve FIXMEs in code
Default variance for topofil counter? (currently same as that of tape)
Rather than forming a linked list of components, solve each as it is identified? Beware of issues like those that revcomplist test checks.
Don't split other traverses at articulating traverses when reporting error stats.
caverot: on RISC OS now fall back to using 2 or even just one screen bank if we can't find a mode where we can create 3 banks [FIXME: need to test this works]
Allow extend (or printing of extend) to unfold right-left instead of left to right?
ISO image? structure debian packages on it as an apt source. autorun for MS Windows?
flag nosurvey legs in .3d file
sort out title which goes in .3d file for this (if no *includes in ... it gets the title of the leafname of this .svx file, otherwise it's the leafnames of the *include-d files, comma-separated):
```
*begin mycave
*title "My Cave"
...
*end mycave
```
make img more modular (convert to C++?)
install file associations for .PLT and .XYZ (check: if we install a non-default right button menu action, does it become default if there are no others?) Mail Larry Fish and Bob Thrun to check if it's OK to include their icons.
add support for .KST? Gary says documentation is out of date, and recent releases of winkarst have broken .KST export/import...
resolve documentation/examples mismatch for station based .XYZ files and implement reading of legs from them.

diffpos: compare connectivity (i.e legs as well as stations) - e.g.

foo.1 moved by (0.02, 0.10, -0.06)
leg between foo.1 and bar.2 removed
...
bar.2 moved by (-0.02, -0.05, 0.03)