Quote:
Originally Posted by kovidgoyal
That's a possibility, the problem is it is not very reliable. You can in principle "remove" a plugin by just deleting its zip file in the calibre config directory. In such a case calibre has no way to run plugin specific cleanup code.
|
If the suggested preference name scheme is followed, then the calibre GUI can, after startup, delete the db preferences for any plugin that isn't loaded. For this check, disabled would need to equivalent to loaded.
If we really want to get fancy, the cleanup code can be included in the preferences and run just before the preferences are deleted.