[GUI Plugin] Import List

[chaley]

Originally Posted by kiwidude

The only additional thing that comes to mind I "could" do in theory is do what Kovid added for the main UI grid of offering a column header context menu for "Adjust width of column for xxx". TBH I think that dialog is overkill (I've only just found it myself) but I can understand it would give you more granular control over a column width. I don't know if Kovid wrapped it up all his functionality in a nice reusable delegate that would make this a trivial change - I certainly wouldn't want to reinvent the wheel by having to recreate it myself.

It is the "class AdjustColumnSize(QDialog)" dialog in gui2.library.views. IIRC it is self contained. It requires a QTableView object. It might work with a QTableWidget as that is a subclass of QTableView, but I've never tried it.

And everything there was requested when the dialog was written.

[kiwidude]

Thanks for that chaley - I will take a look at some point if time permits. To clarify the overkill comment - I've never in (too many) decades of coding and using apps seen anything as comprehensive for a user. I'm sure they love it - I just wouldn't be trying to code it up myself for a calibre plugin grid column. But if it comes for nearly free...

[Rellwood]

https://chatgpt.com/share/680ab946-5...6-5ca6f7e2a541

This is what Open AI has been doing with the Plugin. It still keeps throwing errors though. I have the updated versions if anyone is interested. Im still working on it.

Edit: Updated info

[kiwidude]

@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 ?

[Rellwood]

Originally Posted by kiwidude

@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 ?

I dont think I am making myself clear.

When I import a list. The initial window where I match columns in the list to columns in Calibre - all the columns are default set to max width. I am not doing this. Which isn't too big of a problem, but a pain when dealing with a lot of columns and I have to keep scrolling over. The major problem lies when I click "next"

In the Next screen there are two different viewing panes, the one on the left that has the columns from the list, and the one on the right with the matched books and their matching columns.

My problem is that the title and author columns in the calibre list (on the left pane) are still shown at max width and do not allow for grabbing and shrinking them down. I am left with only being able to see only the title, then scroll over, then ONLY the Author, then scroll over, THEN I can see multiple columns. The Title and Authors are unable to be shown outside of single column view. This is on the Imported List side. The Calibre book list side is fine.

The initial picture is showing how the AI developed the plugin before the attempt to get to the next section which is where the errors show. NOTE that the columns are all evenly spaced.

The Next picture shows what the original import list plugin looks like when I import the same exact list. Every column to match is default set to max -

The final picture shows how the imported list side of the viewer pane to determine if the books match shows ONLY the Title, no matter how far I stretch the pane, it will ONLY show the title, then if I scroll a tiny bit, it will ONLY show the Author. This is just on the List side, the Calibre side is ok, I can move them over. But the List side is ONLY title, ONLY author, THEN you can see the other columns and adjust them.

I hope that makes sense.

Also, Please ignore my pervy books

[kiwidude]

Thanks for the clarification. We were talking about completely different screens - originally you had said “the matching window” which in my head is the Step 2 page with the Matches in library/possible matches for selected book grids. Whereas you are talking about the CSV preview on step 1 and books in list on step 2. Picture worth a thousand words and all that!

I now understand what you mean and can look to make a few tweaks. But I think the easiest solution for now is to either just not use resizeColumnsToContents() on those grids in case of outliers, or use it but then go through and check if any sizes are wider than the current grid width and shrink them down. Also I believe there is a HorizontalScrollMode which can be changed on the grid to Pixel, so it would allow the manual resizing even if your column goes super large by manually double clicking the column header.

[kiwidude]

Release Notes
https://github.com/kiwidude68/calibr...rt_list-v1.9.8

Ive forced a max width of 300 on columns after an autoresize, and changed the scrollbar mode to per pixel so that if you do oversize the column by dragging or double clicking you can always get to the right edge of it by horizontal scrolling to then resize it.

[Rellwood]

Thanks! Works great now! Fixed the issue I had, I appreciate it! Sent donation Cheers!