https://bugs.kde.org/show_bug.cgi?id=425354

--- Comment #7 from David Hurka <david.hu...@mailbox.org> ---
(In reply to Albert Astals Cid from comment #6)
> the code should not break if the
> config files are not "as expected", that's just wrong coding.

Our use of kconf_update is to make the config files “as expected”, but if that
doen’t work reliable, it is understandable to require the code to be tolerant
about kconf_update not working.

I think the simplest solution is to not use the key AnnotationTools but e. g.
LiveAnnotationTools. This key would be new, so there can’t be old tools in its
place. The user would lose the live configuration, but that is probably a minor
issue, since it is “live”.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to