https://bugs.kde.org/show_bug.cgi?id=466997
--- Comment #1 from ratijas <m...@ratijas.tk> --- I guess it's because current code relied on only two sources: app's inherent metadata, and per-user installation per-application overrides file. Thus, we are potentially missing 3 other sources: - system-wide installation's global overrides, - system-wide installation's per-app overrides, and - per-user installation's global overrides. IMHO if the KCM only ever operates on per-user installation's per-app overrides file for writing, then it should at least load all the others and treat them as new default values. However, that kinda complicates things, as now we'd have "default" and "really really the default" states for permissions/resources. For example, I'm was going to implement orange highlighting for changed preferences, and this issue changes semantics of such feature from "differs from default" to "differs from all the rest combined except the very last link in the chain". A bit difficult to comprehend, especially if a user explicitly wants to force-set some certain permission regardless of volatile mid-level overrides. -- You are receiving this mail because: You are watching all bug changes.
