Re: [AD] Sorting objects in the grabber

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


> It's driven by a checkbox in the grabber UI, and the option is saved
> in the datafile, so it's still unsorted when it is loaded back.

Nice, so it's basically a 3-state logic for the grabber: force sorting,
force non sorting, preserve sorting property.

Now how do you translate it for the command line dat utility ? The
straightforward solution would be:
- no option: preserve sorting property,
- '-sort' option: sort,
- '-nosort' option: don't sort,
(that's the way the compression option works). Of course this seems to break
backward compatibility with the current behaviour, although not that much if
new datafiles are created with the SORT property to 'yes' by default and old
datafiles (with no SORT property) are handled as if they were SORTed.

Or this one which preserves strict backward compatibility:
- no option: sort,
- '-keepsort': preserve sorting property,
- '-nosort': don't sort  ?

A solution using only a 2-state logic necessarily misses one case.

--
Eric Botcazou
ebotcazou@xxxxxxxxxx



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/