MobileRead Forums - View Single Post - Possible To-Do List for Future Sigil Releases Post Sigil 1.8

KevinH · 10-28-2021, 01:48 PM

Yes that was what I as proposing. FWIW, PluginRunner gets many of its cfg values from the MainWindow that it is launched from (ie its BookBrowser, etc) so a MainWindow member variable is what the Automate Tool would need to be able to set. It would be easy to create a new AutomateList Tool command "SetPluginParameter" that accepts a single parameter whose value is used to set the MainWindow's member variable value so that PluginRunner can pick it up (empty when not set).

10-28-2021, 01:48 PM	#22
KevinH Sigil Developer Posts: 8,895 Karma: 6120478 Join Date: Nov 2009 Device: many	Yes that was what I as proposing. FWIW, PluginRunner gets many of its cfg values from the MainWindow that it is launched from (ie its BookBrowser, etc) so a MainWindow member variable is what the Automate Tool would need to be able to set. It would be easy to create a new AutomateList Tool command "SetPluginParameter" that accepts a single parameter whose value is used to set the MainWindow's member variable value so that PluginRunner can pick it up (empty when not set).