|
@Rellwood - thanks for posting that, interesting info. Like anything AI from my experience there is a lot of wrong conclusions and paths in there. I originally only read your getting it to analyze stuff, I haven't gone through all the proposed fix stuff that went after (that all looked pretty frustrating)...
The real issue here (that hadn't been spelled out to me or at least not clearly) is if your column is wider than the width of the dialog then the grid will attempt to make sure the next column is completely visible on screen when you scroll right. If it fits then great - the horizontal scrollbar works and you are able to resize that column to the left which is what I was doing in my quick tests. If it doesn't fit then you have a problem because it puts as much of the next column on screen as it can which usually means left aligning and hence giving you no visible grab for the previous column to resize it.
The AI is correct in pointing out that I haven't applied max width restrictions to columns. That was intentional. Otherwise you would then have to handle all the user events like them resizing the window - now the max widths you tried to set have to be changed and it all gets very complicated.
I still come back to you not actually saying what the use case you have here is. The plugin saves column widths - so just like the main calibre window you should be able to size your columns to a "usable" width for 90% of the time that display enough data to be useful. Why do you feel the need to try to max out columns (and triggering this grid behaviour)? Is it because of something I could fix by just adding a tooltip, or ?
|