Quote:
Originally Posted by democrite
Minor note. For plugin runs, possible to keep same file selection afterwards? For example with TagMechanic, easier to rerun if selected files remain. If other plugins make use of such, then it could be helpful for successive plugin runs.
|
The issue is that general plugins can both add and remove resources, change spine order, etc making the plugin runner need ask BookBrowser to do a full refresh.
That said, ... You can do this now with Automate Lists, it will let you store current selections and restore them before the next plugin is run so chains of plugins can be run on the same initial selection but spine order can no longer be assured given a plugin can change that with any addition or deletion. So it is truly safe when the plugin being run does neither.