[KevinH]

Hi,

Yes it is a limitation of the current plugin api but if something like this is important we could add support for it in a future version of the plugin launcher. It could be as simple as always writing a list of selected files "in order" in xml to the temp directory before invoking the plugin. The plugin itself can then decide whether to use that xml list, or work on the entire set of book files, or throw up a gui to select which files you would like to have processed.

Let me think about how that best could be implemented with the fewest number of interface changes that would maintain backwards compatibility.

Kevin