Clean up bmap commands' flags argument

parse_map_flags() silently truncates map flags after the first 't' or
'r'.  This makes it accept arguments "true" and "revert".  However, it
also breaks the perfectly sensible argument "ts", which should show
ships just like "st", but doesn't.

info bmap & friends document arguments "true" and "revert", and also
suggest flags 't' and 'r'.  What a mess.

Make argument "revert" a special case.  Deprecate flag 'r', and clean
up truncation there.

Don't truncate after flag 't'.  If any bad flags follow, ignore
everything after 't', but deprecate that usage.
This commit is contained in:
Markus Armbruster 2011-04-10 07:43:04 +02:00
parent 457f797972
commit a00f9e200e
7 changed files with 64 additions and 18 deletions

View file

@ -79,12 +79,15 @@ A '*' will put all on the map.
When multiple unit types are selected they are displayed
in the following priority order: nukes, land units, ships, planes.
To highlight sectors you own, specify the 'h' flag.
With the 't' flag, the command shows your true bmap rather than your
working bmap.
.s1
.L "Working and true bmap"
.s1
You actually have two bmaps. One which is created by the server; this
one is called your 'true' bmap. You can view your true bmap at any
time using the
.SY "sbmap <SECTS|SHIP> true"
command. However, usually when you view your bmap, you are looking at
time using the 't' bmap flag.
However, usually when you view your bmap, you are looking at
your 'working' bmap. The only difference between your working bmap
and your true bmap is that your working bmap also contains
designations put on there by you using the 'bdes' command, and by your