Quote:
Originally Posted by chaley
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.
|
Since I'm adding a library UUID, I think we'll leave it as is since there isn't really a use case for this at the moment.