Quote:
Originally Posted by ownedbycats
Would a program: connected_device_name('main') conditional on the last action cause anoticeable delay at the beginning of a chain? Removing it seems to have sped it up but it's difficult to measure for sure.
|
Can't really comment much on that. Since you tried and noticed a speed improvement, it must be the reason of the delay.
Quote:
Originally Posted by ownedbycats
Additional question: The action in question is Reading List "sync now." The action greys out in the Reading List menu when no device is connected. Do you know if this means I can probably remove the condition?
Thanks.
|
Don't thinks so. Give it a try and see for yourself.
Quote:
Originally Posted by ownedbycats
Bug?
In the Chain Variables action, the checkboxes for iterate and runtime don't seem to work. On an existing one I can uncheck runtime but not re-check it.
EDIT: Exiting Calibre and ediitng the json file to modify it to true works, but isn't ideal.
|
I cannot replicate this. It works normally for me.
Quote:
Originally Posted by ownedbycats
Enhancement Request, if feasible:
In the conditional dialog, the option to add a custom failure message rather than this:
Code:
calibre, version 6.13.0
ERROR: Cannot run chain: Action Chains: conditions for chain (Read) are not met
This specific chain uses a selection_count() check so I would put something like "Only run this chain on a single book."
|
The condition dialog is crowded enough as it is. The best I can do is to inlucde the condition's toolitp in the error message. Will add this to the next version.