[GUI Plugin] Action Chains

[tamaracks]

Originally Posted by capink

No. That is not possible. And I wouldn't go there. If you need to disable them independently, it calls for using two different chains.

All right, thanks for the answer.

[capink]

Version 1.18.0

• Update: Changes to support python template functions.
• Update: Single Field Edit: Remember last size for interactive dialogs.

[ownedbycats]

I was trying to set up a conditional to run an ask-at-runtime single-field edit if the specified column is empty/undefined. This didn't work, neither did ''. (Also, just to be clear - I was testing with a diffferent book than shown in the screenshot, so not user error.) Do I need to use an if-then template or is there something I missed?

[capink]

It is working for me. I tested with multiple datatypes and it always works. Can you post your chain here?

[ownedbycats]

It started working after a Calibre restart.

[ownedbycats]

Out of curiosity: Is there a limit to how many times different chains could be called?

For example, Chain A calls Chain B. Chain B calls Chain C. Chain C calls Chain D. And so forth. As long as there aren't any calls that would send it into a recursion loop, will it fail after x many calls?

[capink]

Theoretically no. But I have not tested this extensively. Also infinite recursion should be detected during the validation phase, before the chain runs.

[ghoetker]

Thank you for this great contribution. I would like to run the Extract ISBN action followed by Download Metadata and Covers. To do so, I need to hit the "Yes" button in the dialog that Extract ISBN displays after completing. I can't figure out how to do so, meaning the Download... action fires before the ISBN is added.

Hopefully I'm missing something obvious. Guidance very appreciated.

Thank you.

[ownedbycats]

capink: I thought perhaps the "prompt for confirmation" module sandwiched between two actions would work as it temporarily halts the chain until confirmation is given. But I tried and it means you can't click on anything else, including Extract ISBN's dialog. Is this work-aroundable?

[capink]

I cannot keep catering to every plugin out there. The solution is either in the Extract ISBN plugin if the maintainer is willing to change its behavior, or someone writing a module that works around this problem. I don't use the Extract ISBN plugin myself, so don't have much knowledge/experience with it.

[ownedbycats]

Ok, I wanted to check something. Here's what I found:

At first, I thought "wait until any jobs started..." wasn't working when I tried— that's why I didn't mention it in the previous post. Then I realized something and here's what I think is happening:

Some plugins have a confirmation to update the library. (According to this post it's a Calibre requirement to prevent db collisions/conflicts.) This confirmation uses a self.gui.proceed_question() dialog, which is the type that pops up in the lower right hand corner with yes/no/other options.

Count Pages, Extract ISBN, and FanFicFare are the three I know of and tested with. Calibre uses it for a few things too, bulk metadata downloads is one.

When I tested: Action Chains waited for the jobs to finish, but did not account for the confirmation and immediately fired off the next action.

[capink]

That is because I am able to detect the jobs easily by:

• Query the job manager of all running job ids immediately before the action is launched and storing them.
• Query the job manager of all running job ids immediately after the action is launched and storing them.
• Figuring out which jobs were started by the action itself, by subtracting the first set of job ids from the second set.
• Keep blocking the GUI until all the jobs started by the action are finished.

I never used any of the plugins you cited, and have no experience with proceed_question. If anyone can provide the code to detect proceed_question dialog in the middle of the action in a robust way, I will add it to the plugin.

[Terisa de morgan]

Originally Posted by ownedbycats

Ok, I wanted to check something. Here's what I found:

At first, I thought "wait until any jobs started..." wasn't working when I tried— that's why I didn't mention it in the previous post. Then I realized something and here's what I think is happening:

Some plugins have a confirmation to update the library. (According to this post it's a Calibre requirement to prevent db collisions/conflicts.) This confirmation uses a self.gui.proceed_question() dialog, which is the type that pops up in the lower right hand corner with yes/no/other options.

Count Pages, Extract ISBN, and FanFicFare are the three I know of and tested with. Calibre uses it for a few things too, bulk metadata downloads is one.

When I tested: Action Chains waited for the jobs to finish, but did not account for the confirmation and immediately fired off the next action.

I don't know FanFicFare, but for CountPages and ExtractISBN, you can configure them to not showing the confirmation, so it would work.

[ownedbycats]

Ah yeah, I forgot about the option to disable the confirmation in kiwi's plugins.

I'd think that should work, though I suppose there is a slight chance that the second job begins a split-second before the db write actually occurs.

[Terisa de morgan]

Originally Posted by ownedbycats

Ah yeah, I forgot about the option to disable the confirmation in kiwi's plugins.

I'd think that should work, though I suppose there is a slight chance that the second job begins a split-second before the db write actually occurs.

Sorry, I have to care about those things at my day work, I forget them here