Secondary sorts in Widget.SortableTable 0.21 always seem to be
descending, independent of the columnSpecs for that column, which
looks a bit odd if it's anything but a date... was there a reason
behind that? If not, would a fix be something the author would want to
handle, or should i bang on it some more? (I've already de-frameworked
[widgetified?] it for my application, which was fairly simple, but
understanding the sorting code looked like actual work. ;-)
Thanks,
alex.
I'm the author, and patches are welcome ;)
Seriously, the secondary sort should follow the rules for defaulting:
* If a direction is explicitly specified for that column, use it.
* Otherwise look at the type and use the default for that type (aka, dates
descending, everything else ascending).
* If we can't figure out the type, use ascending.
So if the secondary column sort bits aren't working like that, there's a
bug.
-dave
/*===================================================
VegGuide.Org www.BookIRead.com
Your guide to all that's veg. My book blog
===================================================*/