Yes Sorting arrow is left behind as you say.
Personally, if i've set a sort order, i don't want it changing unless i change it
So, to answer this.... "I'm not sure how and when to remove user sorting." ...would be to have it install with a default sort setting (arrow visible) of none, or age, newest first, then before searching, save that setting to re-apply later if it does not match the default, then let it do as it does now during search and then re-apply the selection that was previously set.
The problem is that results are returned already sorted by some criteria and I'm not sure it's a good idea to force sorting again
.... no different to me doing it manually.
I think that it's not just NZB.cc tab, but all tabs.
.... hmmmmm, i didn't think so {goes to check with a test
}
Results - using
Rosetta.Stone greek as the search string, and using
NZBIndex and
NZB.cc tabs for comparison, set both tabs to sort by age, newest first, then use the global search for given string, then go to each tab and look at results, then click the age column button twice to sort them as requested, and perform the search again, and you will see the NZB.cc tab loses it's sort request
Second Test.
To try and understand what you were talking about, i then applied a sort by subject filter, and performed the search again, and the NZBIndex tab sorted by age, newest first, even though i had it set to sort by subject.
So, i see what your getting at...... i'd still say the same though as i did before, apply a default sort by age, newest first unless a review of that setting gives a different setting, and then re-apply that setting after the search has completed, much like a macro command action
EDIT:
now using v0.37.2
And thank you, for taking the time to explain the results come back pre-sorted, and explain why i am seeing the odd effeects i am
