[DiapDealer]

@KevinH:

I think they're probably referring to a recent discussion in my TagMechanic plugin thread. I mentioned that there's no current way from within Sigil for custom parameters to passed to plugins via automation list runs.

I had speculated on whether it would be feasible to provide an optional argument to Sigil's plugin launcher code, that would allow the parameter field of an automated list's step to be made available to a plugin.

String only. Could be a simple as something to let the plugin know that it IS, in fact, running as part of an automation run. Could be something as complicated as a json string that a plugin could serialize. It would be up to the plugin dev to decide what goes in the parameter field, and how their plugin would use it.

All speculation though. I don't even know if it could be easily incorporated. But to be clear: the last thing I was suggesting was any kind of Sigil-compliance-based parameter syntax that all plugin-devs would need to adhere to. Just an optional string value they could use in any way they saw fit in their plugin's code--IF--they wanted their plugin to behave differently during an automation-list run.

Otherwise, I agree: Sigil was never geared toward being "fully automated". This new automation-list feature should not be seen as something that's going to continue to evolve very much. Based on the plugin included, dialogs are going to pop up, questions are going to need to be answered from time to time. We're not going to force all of our plugin devs to alter their plugin code just because someone has included it in an automation and doesn't like making a few selections.