[GUI Plugin] View Manager

[ownedbycats]

The last Calibre beta had a bug that caused crashes when renaming saved searches. There were some changes made in 5.4.x to fix that, but I'm not sure if any of them affected the caches.

I think there was also a recent change to allow templates in saved searches, which I imagine would affect the caches.

[JimmXinu]

I've opened a calibre bug report.

FYI, changing library will also update the list.

[chaley]

Originally Posted by JimmXinu

VM calls calibre.utils.search_query_parser.saved_searches() each time the VM config dialog is opened.

That method appears to be caching it's results now and giving VM the same list each time. Or else it's not using the same Saved Search cache as the rest of Calibre?

You should use db.saved_search*, which is what calibre has used since V4 and possibly before. The list of methods is found at the end of calibre.db.legacy. The same methods exist if you have a new_api db handle.

[JimmXinu]

Originally Posted by chaley

You should use db.saved_search*, which is what calibre has used since V4 and possibly before. The list of methods is found at the end of calibre.db.legacy. The same methods exist if you have a new_api db handle.

Inherited plugin dating back to the calibre 0.9 days. As long as it ain't broke, I don't fix it.

But since it's broke...

Switching to gui.current_db.saved_search_names() as suggested appears to work fine. Test version in a minute.

[JimmXinu]

New Test Version Attached

2020-11-02
- Change how saved searches are retrieved to newer API.

2020-10-30
- Apply persist_shortcut to view actions when Calibre >= v5.4 so view shortcuts aren't discarded as easily. Calibre PR #1246

2020-10-22
- Add 'Re-Apply Current View' action. Only available when a view has been previously applied.

[compurandom]

I can confirm the saved searches issue is fixed and apply current view works, at least with 5.3 / beta from #335.

[JimmXinu]

New Version Released

Version 1.6.0 2020-11-04
- Change how saved searches are retrieved to newer API.
- Apply persist_shortcut to view actions when Calibre >= v5.4 so view shortcuts aren't discarded as easily. Calibre PR #1246
- Add 'Re-Apply Current View' action. Only available when a view has been previously applied.

[ownedbycats]

Not sure how much work it would be to implement, but an option to automatically switch to a specific view when a device is connected might be useful.

[ownedbycats]

Is there a limit of how many columns I can sort by? Some books are sorting unexpectedly and I'm not sure if it's user error or not.

[JimmXinu]

I believe calibre has a limit somewhere in tweaks.

[ownedbycats]

I found a maximum_resort_levels and increased it. I think it worked. Thank you.

I also found sort_dates_using_visible_fields, which might also account for some of the weirdness.

[ownedbycats]

I'm a little confused by the sorting order of non-Reading List books here:



- The device is plugged in, so "On Device" sorts first.

- Then it also sorts by "On Kobo." (The lock doesn't reflect the value of the column itself; it just means that #kobocoll has "Kobo Store" in it).

- Then the books I'm currently reading (comp column that returns "true" if #read, #lastread, and #percentread all match certain values) sort to the top.


- Then it sorts by the reading list. I use the pseudobool "on Reading List" so that I can sort RL in ascending order and still have it appear on top. (Unfortunate side effect is that any RL books being read sort to the top, but I can live with that.)

However, after all of that it should sort the Currently Reading books in descending order by #percentread, and then sort any with the same percentage (e.g. 100% for fully read) by date.

Instead, I get what I see in the screenshot.

I have maximum_resort_levels = 12.

Any idea what I'm doing wrong here?

[ownedbycats]

Update: I figured it out. Even though "Percent Read" column pulled directly from the "%" column (I use one for column view, the other for book details), somehow it was mucking up the sorting.

ANOTHER EDIT: It was set to sort by integer instead of text, and since the original column is {0}% the percent sign tripped it up.

[Rellwood]

I was wondering if it is possible to update the plugin to edit current view and keep the name?

example:
I have a "read books" view which shows all the books and each individual read date column (there are 8 columns Dr1, DR2, DR3 etc.) a latest read date, a Goodreads Read date, a read status column etc.

Today I decided to make use of the Goodreads Sync plugins' ability to add the goodreads date started for books in the "currently reading" shelf of Goodreads. So I created a column GR_Date_Started. It will be used in the "Read Books" view.

I cannot seem to edit the view using the view manager plugin for customizing the plugin. It shows all the checked columns in the view, I can check off the new column I want to add, but I cannot seem to move the column in the proper position in the view.

I cannot just update the "read books" view by saving the current view with that name.

All the newly saved view names need to be unique, making it impossible to simply edit or update a current view without renaming it and deleting the old view and then renaming that new view with the desired name.

Surely there is a way to "update current view" without having to come up with a unique name.

[ownedbycats]

Did you try "save view columns"?