If you can run from source, please do ...

[chaley]

There are some changes pushed to source today that improve the GUI performance when scrolling. The more composite columns you have, the more the improvement. It does this by not processing a book for details display until the selection hasn't changed for 100ms. As a result, the book details display(s) update 100ms after scrolling or paging stops.

It also changes the semantics of db.get_metadata() (not ProxyMetadata()). Composite columns are now evaluated when they are used instead when get_metadata() is called. I checked to be sure it worked in all places where calibre uses get_metadata(), but it is possible that some plugins do things that "go around" the rules by reaching inside a metadata object in ways we don't expect. This is the reason I hope people can run it, as there is no way I can simulate how people use which plugins.

[Comfy.n]

Sure, I hope I can find something worth mentioning, as I can't really figure what plugins use those functions, and I myself use just the functions explained in examples provided on the forum.

I only remember seeing db.get_metadata() before, because it is used in a search to find all items (e.g. authors) that have an attached note.

I'm currently testing some Action Chains and navigating the UI, everything seems to run smoothly.

BTW, those interested in testing on Windows can follow the steps below, although that's not recommended on a working/main library, please correct me as needed:

- download this file
https://github.com/kovidgoyal/calibr...ads/master.zip

- extract for instance to c:\users\username

then run the following calibre-dev.bat

set CALIBRE_DEVELOP_FROM=C:\users\username\calibre-master\src
start calibre

[Terisa de morgan]

I don't think I'm able to run from source code (not enough time), but I'll take into account as I even have some plugins for myself that using a lot get metadata... and I've got a lot of composite columns.

[JimmXinu]

I'll run it for a while--I don't see any immediate issues.

[DNSB]

Looks okay here but I'm not a heavy custom column user.

[ownedbycats]

I'm a heavy composite column user. Much smoother.

[JimmXinu]

I'm not seeing any issues with the plugins I regularly use that update custom columns: FanFicFare, Reading List, Manage Series and Count Pages.

[chaley]

Originally Posted by Terisa de morgan

I don't think I'm able to run from source code (not enough time), but I'll take into account as I even have some plugins for myself that using a lot get metadata... and I've got a lot of composite columns.

FWIW: if you can, you should use get_proxy_metadata() instead of get_metadata(). Proxy metadata uses lazy evaluation for all field accesses, making it much faster for applications that use some of the metadata from a book.

It is usually a direct replacement for get_metadata(). However, it can't be used if you use mi.set() to modify the metadata. Other metadata methods that can't be used are smart_update(), template_to_attribute(), set_user_metadata(), set_all_user_metadata(), set_identifier(s)(), remove_stale_user_metadata(), and all_non_none_fields().

[Terisa de morgan]

Originally Posted by chaley

FWIW: if you can, you should use get_proxy_metadata() instead of get_metadata(). Proxy metadata uses lazy evaluation for all field accesses, making it much faster for applications that use some of the metadata from a book.

It is usually a direct replacement for get_metadata(). However, it can't be used if you use mi.set() to modify the metadata. Other metadata methods that can't be used are smart_update(), template_to_attribute(), set_user_metadata(), set_all_user_metadata(), set_identifier(s)(), remove_stale_user_metadata(), and all_non_none_fields().

Thank you! I'll look at it because I think I remember to use A LOT get_metadata (I did a long time ago and I don't change it a lot nowadays).

[BeckyEbook]

From which version of Calibre can you use get_proxy_metadata?
I'd like to consider whether it's worth changing the minimum version in the plugin code, or whether to add code to maintain backward compatibility.

[chaley]

Originally Posted by BeckyEbook

From which version of Calibre can you use get_proxy_metadata?
I'd like to consider whether it's worth changing the minimum version in the plugin code, or whether to add code to maintain backward compatibility.

Version 1.0

[BeckyEbook]

A man learns all his life

[ownedbycats]

Originally Posted by chaley

Version 1.0

Wasn't 1.0 still called libprs500?

[chaley]

Originally Posted by ownedbycats

Wasn't 1.0 still called libprs500?

It was called calibre when I started working on it in 2010. I don't remember the version. Perhaps 0.7.

[ownedbycats]

The earliest changelog I find is for 0.7. It indicates that 0.6 was also called Calibre.