Quote:
|
The font and title boxes are shown because it is using the general template tester...
|
I didn't mean to criticize the functionality— it is quite clear that the template tester is necessary, I have used the calibre template language once before to extract metadata from books.
I just meant that I personally tried a dozen times to get the book title to switch to show the value of the template I was trying to use instead lol. Once I understood that book details did not actually pertain to the template value I wanted I gave up trying to click and actually read the instructions (
https://www.mobileread.com/forums/sh...&postcount=172)
I assumed that changing the font is generally done a single time even for a long program and just makes the UI cluttered— though I'm sure it has it's uses and it isn't at all confusing what it is for. I copy paste stuff if its long anyways.
Quote:
|
As regards "terribly slow"...
|
Sorry for the confusion, I just mean that I can see obvious improvement in the way I made the chains work. It is relatively slow, not absolutely.
I have around 15k books in my main calibre library, I was mostly exaggerating about the speed. You're right, changing the layout is hardly longer than loading the database.
I only mentioned it because I think I am unnecessarily loading covers when I do not need to. I assume that if I do not load the covers, it will eliminate the quite fast loading time. If I turn off covers before switching libraries, there would be no loading time, the button pushing in this order (using action chains) might actually be faster.
In short, it is my implementation that is the slow part, not the plugin at all! Since it was my first try, I did not get around to using the chain caller action you suggest but I will try it next for nth library I have.