|
If we wanted, we could make that warning only in C++ PluginRunner code before launching any output plugins and not use sigil.cfg at all nor change any of the launcher/wrapper python code.
Alternatively, we pass the dirty flag to the plugin and let the plugin code produce the warning and handle it.
Are there any other uses for the dirty flag that would make it useful inside the plugin?
|