sortInitialOrder reset

[severa]

Hi. Nice tool. One thing that might be helpful would be to enable the ability to reset sortInitialOrder for a column if a different column is selected for sorting. In other words, if I select column 0 (which sorts by its sortInitialOrder) then I select column 1 (which sorts by its sortInitialOrder) but then I select column 0 again, it will sort by !sortInitialOrder. This does not feel natural when moving between columns, imho. I believe in order to achieve this the default sort state would need to be 'reset' for any column that is 'selected away from' (or brute-forcely, all columns that are not selected). I guess ideally it would be possible to have a property to allow the coder to specify whether s/he wants that column's sortInitialOrder reset when selecting other columns. thoughts?

[Mottie]

Hi Severa!

Hmm, that sounds like a good idea! I'll add it to my to do list :)

[Mottie]

Ok!

I've added a new option named sortRestart (since sortReset was already used) which seems to work as you expect; but it might do a little something odd when you click on a column after multi-column sorting. Here is how to duplicate the wierdness (if it really is that bad):

• Sort the first column (now in sortInitialOrder)
• Next, shift sort the second twice (so it's in !sortInitialOrder
• Lastly, click (no shift) on the second column. It will sort in the !sortInitialOrder direction...

It doesn't seem that bad, but I wanted to see what you thought,

[severa]

Hi Mottie. Interesting, I am using 'desc' sortInitialOrder and this change seems to cause that setting to be ignored. So while it now does restart from sortInitialOrder each time you switch back to a column, it only works for 'asc' sort order (in fact, that setting seems hard-coded now). Was that intentional? I also noticed that the value does not seem to be able to be applied via a header (ie to override for a specific column). Was that also intentional?
I agree that the shift sort option introduces a tricky situation (actually that is the same behavior as before the change so maybe the caveat can be that sortInitialOrder does not apply to multi-column scenarios? :-) ).

[Mottie]

Hmm, it's a bit more complicated than I thought... give me some time to work on a fix :P

[severa]

:-) Yes, I thought it might be. Sorry about that. But I do think its a useful feature. One scenario where I think its particularly helpful is when you have table that consist of similar statistics over multiple time periods (eg test score results for different years). A common use-case in that situation is to want to know who was the top performer in a single year, then the top performer in another year. Or the lowest performer, or top 5 performers, etc. With that kind of homogenous data, it is beneficial to be able to easily make such comparisons by column with only a single click. Thanks!

[Mottie]

Just letting you know that I'm still trying to fix this bug. If I can't get it by this weekend, I'll save it for the next update.

[Mottie]

Grrr, I didn't get this fix included in version 2.1... but I'll keep working on it. Sorry!

[severa]

Ok, sorry for the frustration. :-)

[Mottie]

Okie dokie, I think I finally got it fixed! YAY!!

Check out the new demo in version 2.1.1.

[Mottie]

Well, I guess it's working? I'm going to go ahead and close this issue. If you find any problems with the updates, please feel free to reopen this issue. Thanks!

[severa]

Sorry, I haven't had a chance to test it thoroughly. I will try over the weekend. Thanks!

#end

On Mar 16, 2012, at 9:22 PM, Rob Greply@reply.github.com wrote:

Well, I guess it's working? I'm going to go ahead and close this issue. If you find any problems with the updates, please feel free to reopen this issue. Thanks!

---

Reply to this email directly or view it on GitHub:
#30 (comment)

[severa]

Hi Mottie. Thanks a lot for this, this is perfect! Sorry for the delay.