Quote:
Originally Posted by BetterRed
As you can guess I like it. Can I assume changes to the LT Editor will be inherited by NV?
I have to ask, possibly again - why can't NV include the Comments [dc:description] column?
BR
|
[1] That would be a bad assumption, since it is not that simple. In the beginning, in late 2018, my new Entities Manager plugin made its own revised copy of Calibre's Editor to work within EM as its "Entity Note Editor", which at that time used PyQt5.QtWebKitWidgets. QtWebKit was deprecated in Qt 5.5 and removed in Qt 5.6. So, Entities Manager had to update its copy of Editor to support QWebEngineView instead. For Calibre 6, I changed the EM Editor to use qt.core instead of PyQt5. Notes Viewer now has a slightly revised copy of the current EM Note Editor.
[2] As I said once before, "Comments" is a Standard Column, not a Custom Column. Apples and Oranges. Never the twain shall meet. NV was designed and developed both implicitly and/or (especially) explicitly to use:
- Only fields found in field_metadata.custom_field_metadata()
- Only fields starting with a "#"
- mi.get_user_metadata()
- mi.set_user_metadata()
To add an exception for even a single Standard Column would be ugly, offensive to my structured programming sensibilities, bug-inducing, a lot of work, and generally a PITA. No thank you.
If it really matters that much to you, evaluate the cost-benefit ratio of cloning the Standard Comments Column in a new #column, and use chaley's "Save Composite Custom Columns" plugin to hard-copy the data into it every time Calibre closes.
I gather that the beta test version is cleared for normal release.
DaltonST