[GUI Plugin] Action Chains

[justinmiller87]

Originally Posted by capink

If my memory serves me right, the plugin checks if the new value is equal to the old value (and in case of authors column it doesn't take different author order as different), and if they are, it does not apply the value to prevent changing last_modified column, which would in turn trigger changing opf files on disk and slow things unnecessarily.

Chaley has since introduced a change in calibre source that does a similar thing, so when I get time to look at the code I might remove this.

In the mean time, to get around this, the solution is to change the author string by adding an action that adds a "temporary" to the author list, and then sort and remove the temporary string in the next action.

Attached is a chain that does what I describe above.

I appreciate your help. That resolved it.

[ownedbycats]

Has there been any thought into making per-library chains, aside from restrictions? I have a second library now for my wishlist and most of my main-library chains are useless for it.

[Terisa de morgan]

Originally Posted by ownedbycats

Has there been any thought into making per-library chains, aside from restrictions? I have a second library now for my wishlist and most of my main-library chains are useless for it.

YES!, please. Because of this, my action chains are all included in menu entries with the name of the library. I would like something safest.

[capink]

Originally Posted by ownedbycats

Has there been any thought into making per-library chains, aside from restrictions? I have a second library now for my wishlist and most of my main-library chains are useless for it.

When the plugin was in the initial phases of development, it was put forth whether the chains should be library specific or global. There was not much traction for the library specific option, so the plugin continued with the global option.

Originally Posted by capink

Another thing I am not sure about, is whether it makes sense to make the chains library specific, or keep them as they are now. If people have any input about this, I would be interested in hearing it. It might break existing settings though.

It was a binary either/or choice. The idea of making the plugin support both invites a lot of complications in coding as well as in the interface of the plugin, that I am not ready to deal with right now. I am not going to rule the possibility altogether, but if it ever happens it is not going to be anytime soon.

Originally Posted by Terisa de morgan

YES!, please. Because of this, my action chains are all included in menu entries with the name of the library. I would like something safest.

If your main concern is safety, you can set the following condition on your chains:

template: program: current_library_name()
comparison operator: =
value: the name of your target library

This will make sure the chain does not run accidentally in libraries it is not intended to run in.

[ownedbycats]

Possible bug with an interaction between Reading Goal and Action Chains and multiple libraries.. I not sure which plugin responsible so I put both threads.

Steps to replicate:

1. In Reading Goal for Library A, have a challenge set.
2. Put "Add to Challenge > <challenge name>" in an action chain.
3. Open Calibre in Library B.
4. Copy book to Library A, and then switch.
5. Run the action chain.

It fails to validate, and when I open the Calibre actions in AC, it shows "no challenges" despite there being a challenge.