feature request #8045
Improve handling of default values and override in local preferences
0%
Description
For selection of default, dbPreference or explicit local value the local preference pages should have combo boxes.
Depending on his selection the local preference should be handled:
- default: save the default value
- db preference: delete the value in local preferences if exist
- exlicit value: save to preference file
Related issues
History
#1 Updated by Andreas Müller 3 months ago
I don't know if we really need "db preference" as explicit value. It makes it more difficult to understand and there is almost no added value (compared to "default". So we only need "default" and the list of explicit values. If "default" is chosen then the preference is deleted from the local preferences.
#2 Updated by Katja Luther 3 months ago
I would show the value of the db preference in the drop down, but with ("global") or ("db") behind
#3 Updated by Andreas Müller 3 months ago
Katja Luther wrote:
I would show the value of the db preference in the drop down, but with ("global") or ("db") behind
OK, if this is not an explicit entry but if it is only added to the anyway existing entry for this value. Maybe "recommended" is another possible label. A bit long but standard for many such cases.
#4 Updated by Katja Luther 2 months ago
- Related to bug #7856: Allow local override for distribution vocabularies added
#5 Updated by Andreas Müller 2 months ago
- Related to bug #7849: Improve DB Preferences handling and saving in TaxEditor added
#6 Updated by Andreas Müller 2 months ago
- Subject changed from local preferences pages with drop down to Improve handling of default values and override in local preferences
#7 Updated by Andreas Müller about 2 months ago
- Target version changed from Release 5.6 to Reviewed Next Major Release
