Wrong column width for book row number in marked books after deletion of a marked book

Bug #1486398 reported by Raúl Núñez de Arenas Coronado
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Fix Released
Undecided
Unassigned

Bug Description

Calibre 2.35
Windows 10 x64

After the fix for bug https://bugs.launchpad.net/calibre/+bug/1482993, when you delete a book which was marked and had a large book number the mark icon appears partly over the book number. I've attached an image.

It happens when you delete a marked book with a number which occupies all the column and no other marked books are present in that particular screenful of books.

It had never happened prior to the fix for bug 1482993.

Revision history for this message
Raúl Núñez de Arenas Coronado (dervishd) wrote :
Revision history for this message
Kovid Goyal (kovid) wrote :

Once again, I cannot replicate this, but I have made some changes that might help. Try it and see.

Revision history for this message
Kovid Goyal (kovid) wrote : Fixed in master

Fixed in branch master. The fix will be in the next release. calibre is usually released every Friday.

 status fixreleased

Changed in calibre:
status: New → Fix Released
Revision history for this message
Raúl Núñez de Arenas Coronado (dervishd) wrote :

Thanks A LOT, Kovid, and sorry for bothering you with this minor, cosmethic problems O:)

I'll try the new version.

Revision history for this message
Eli Schwartz (eschwartz) wrote :

I just noticed the problem on a VL with only 75 books (it went went away after manual resizing)... I can confirm the fix worked on v2.35.r10

Also, I noticed at some point (I have no idea when and was too lazy to report it :o ) when you mark books the numbers+pin on marked books is misaligned from the number on unmarked books. This is now fixed as well.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.