bug #7849
Updated by Andreas Müller over 5 years ago
Currently it often happens that DB preferences are not (correctly) saved if pressing OK or Apply in DB preferences dialog. We need a framework that makes it easy to always handle save of preferences correctly. The framework may include: * a registry which returns a list of all available pref.predicates, including the expected default values (for all predicates allow override = true must be part of the default value) * when opening TaxEditor and when opening the DB preferences view all registered values are freshly read from DB * when opening pref view all values are written to the UI including values for allow override * when saving cache is emptied and reloaded for registered list of predicates, all values are read from the UI (if available there), only those values NOT yet handled via UI must NOT be deleted from cache (theses might be experimental feature with no configuration UI available yet) * when saving all predicates of the registration are saved to database * if value+allowOverride = default value => delete * otherwise: save value (API will decide if create or update is needed