Calibre 6.x sorting and multiple selection work differently than 5.x?

[WormGod]

Apologies if this is not the correct spot for this. Didn't see a general questions thread.

I recently upgraded from 5.44 to 6.2.1, and I noticed the the following behaving differently in 6.2.1 than in 5.44 (and all the earlier versions that I remember using).

1. Calibre no longer remembers the last sort setting. For example, I can sort by date added (descending - most recent on top) by clicking on the Date column twice. Next, I highlight a book and click on the Author column to sort by Author and see all books by that Author. If I then click on the Date column again, Calibre sorts the books by Date but in Ascending order (oldest on top). Older versions of Calibre used to go back to the previously used sorting method (descending in this case).
Is this intended, or is there a setting that I can change to get the old behavior back?

2. Calibre now only clears a multiple selection by either clicking outside that selection or on the row number (or other non-editable column) of one of the selected books. For example, I can select multiple books by clicking on one and shift-clicking on another. Previously, I could clear the multi-selection and select only one book within that multi-selection by clicking anywhere on the row for the book I wanted to highlight. Now, if I click on any editable column within that multi-selection, that field is in edit mode, and the multi-selection stays active. Causes a bit of a problem if I want to edit the metadata of one book and not all those that had previously been selected. If I click on a book not within the multi-selection or on a non-editable column within the multi-selection, the multi-selection is cleared.
Is this intended, or is there a setting that I can change to get the old behavior back?

Thanks!

[DNSB]

Originally Posted by WormGod

1. Calibre no longer remembers the last sort setting. For example, I can sort by date added (descending - most recent on top) by clicking on the Date column twice. Next, I highlight a book and click on the Author column to sort by Author and see all books by that Author. If I then click on the Date column again, Calibre sorts the books by Date but in Ascending order (oldest on top). Older versions of Calibre used to go back to the previously used sorting method (descending in this case).
Is this intended, or is there a setting that I can change to get the old behavior back?

I suspect that since you are clicking again on the Date column, it is toggling the setting between ascending and descending instead of just switching to the date column for sorting. This matches the behaviour on the other sortable columns.

Originally Posted by WormGod

2. Calibre now only clears a multiple selection by either clicking outside that selection or on the row number (or other non-editable column) of one of the selected books. For example, I can select multiple books by clicking on one and shift-clicking on another. Previously, I could clear the multi-selection and select only one book within that multi-selection by clicking anywhere on the row for the book I wanted to highlight. Now, if I click on any editable column within that multi-selection, that field is in edit mode, and the multi-selection stays active. Causes a bit of a problem if I want to edit the metadata of one book and not all those that had previously been selected. If I click on a book not within the multi-selection or on a non-editable column within the multi-selection, the multi-selection is cleared.
Is this intended, or is there a setting that I can change to get the old behavior back?

I've seen that behaviour and according to the various OS interface standards it is incorrect. Clicking on a single item in a selected group should deselect the other members. Not sure if this is a calibre issue or if Kovid is going to be working around another QT6 glitch.

[theducks]

there is a tweak that affects how many layers of sorts bias the results. I believe the default is 5
FWIW I set to 3

[Comfy.n]

Originally Posted by WormGod

Apologies if this is not the correct spot for this. Didn't see a general questions thread.

I recently upgraded from 5.44 to 6.2.1, and I noticed the the following behaving differently in 6.2.1 than in 5.44 (and all the earlier versions that I remember using).

1. Calibre no longer remembers the last sort setting. For example, I can sort by date added (descending - most recent on top) by clicking on the Date column twice. Next, I highlight a book and click on the Author column to sort by Author and see all books by that Author. If I then click on the Date column again, Calibre sorts the books by Date but in Ascending order (oldest on top). Older versions of Calibre used to go back to the previously used sorting method (descending in this case).
Is this intended, or is there a setting that I can change to get the old behavior back?

I too have noticed something odd when sorting in 6.0+ versions.

Versions 5.44 and older behaved differently, in my view. But I can't tell what changed.

[kovidgoyal]

1. is a bug caused by a change in Qt 6 now fixed. https://github.com/kovidgoyal/calibr...659e99229424c6

2. is also a change in Qt 6, but not one I feel inclined to work around.

[DNSB]

Originally Posted by kovidgoyal

1. is a bug caused by a change in Qt 6 now fixed. https://github.com/kovidgoyal/calibr...659e99229424c6

2. is also a change in Qt 6, but not one I feel inclined to work around.

@kovidgoyal: Wondering if you indulge in pleasant daydreams about something humorous and lingering, with boiling oil or molten silicon and QT's devs.

[kovidgoyal]

Originally Posted by DNSB

@kovidgoyal: Wondering if you indulge in pleasant daydreams about something humorous and lingering, with boiling oil or molten silicon and QT's devs.

Always, it's how I while away the endless hours of boredom between bug reports

Seriously though, for all its quirks and bugs Qt has provided me with far more value than the annoyance it causes. I am grateful for the efforts of all the people involved in it.

[WormGod]

Originally Posted by kovidgoyal

1. is a bug caused by a change in Qt 6 now fixed. https://github.com/kovidgoyal/calibr...659e99229424c6

2. is also a change in Qt 6, but not one I feel inclined to work around.

Thanks for clarifying that I am not imagining things.
And extra thanks for fixing #1!