[ACK] Request: change how "Last Updated" column sorts in Library

When I click on the Last Updated column in Library I am interested in seeing the most recently updated resources on top (that is, sorted most recently updated to least recently updated). The normal first sort is just the opposite, from the oldest to the newest. This makes me have to click the column heading twice to get what I want to see..

Please change the behavior so that on the first sort the column sorts recent to oldest. To get this information is why the column was added, and I am sure almost all of us use it that way.

Find more posts tagged with

Comments

Bruce Dunning

Please change the behavior so that on the first sort the column sorts recent to oldest.

Great suggestion.

NB.Mick

https://community.logos.com/discussion/comment/734589#Comment_734589

Please change the behavior so that on the first sort the column sorts recent to oldest.

Great suggestion.

yep, that's why it has been made before (Rosie? MJ?) and some people found this to be a feature parity issue (to phrase it as Denise might: Windows users getting the attention of stepcousins three grades removed, as usual). I really did expect this for the current beta....

JT (alabama24)

https://community.logos.com/discussion/comment/734596#Comment_734596

Windows users getting the attention of stepcousins three grades removed, as usual

What! Bob bleeds MSFT. [:o]

Jack Caviness

https://community.logos.com/discussion/comment/734596#Comment_734596

Windows users getting the attention of stepcousins three grades removed, as usual).

It must be painful to have your tongue planted that firmly in your cheek—or in this case, in both cheeks at once. [:^)]

BTW, Mark, it does sort that way in the Mac version

SineNomine

This is a silly feature difference between Mac and Windows. I suspect that it's just been overlooked.

Dylan Rondeau

https://community.logos.com/discussion/comment/734704#Comment_734704

This is a silly feature difference between Mac and Windows. I suspect that it's just been overlooked.

There is an active case to correct this behavior on Windows, but I don't have an estimate on when it will be implemented. I've added this thread to the case notes.