View Single Post
Old 03-19-2022, 08:36 AM   #16
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,495
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
@kovid: the problem happens because gui2.library.views.restrict_column_width() is called before the main window is resized. At startup the (undisplayed) main window appears to be 100px wide so the calculation of the maximum space available for a column is incorrect. The sizes don't become correct until all the various events are processed, which is at the end of initialization.

I have a fix but I worry that it is not optimal or even correct. I changed restrict_column_width() to do nothing until all of the events to repaint the screen are processed (the same as quickview initialization). This required added an "initialization_complete" boolean to ui.py that restrict_column_width() checks. I can push a PR with these changes if you want to see them.

Edit: restrict_column_width() appeared with pin views.

Edit 2: my guess is that Qt changed how and when some resize and repaint events are processed.


EDIT: see post 19 below

Last edited by chaley; 03-19-2022 at 01:33 PM.
chaley is offline   Reply With Quote