[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: Uninitialized config values
From:       Kevin Funk <krf () gmx ! de>
Date:       2013-11-16 23:44:40
Message-ID: 4680908.LW9XMOJx8s () kerberos
[Download RAW message or body]

Am Sonntag, 17. November 2013, 01:19:05 schrieb Alex Turbov:
> On Sun, Nov 17, 2013 at 1:13 AM, Dominik Haumann <dhaumann@kde.org> wrote:
> > Now your question how to fix this: Initialize all variables of the global
> > instances. The initialization value does not matter, because it's
> > immediately
> > overwritten by readConfig().
> 
> alternative way: use .kcfg file and generator...
> when configuration became fatty C++ code became even more fatty (and worse
> maintainable)...
> 
> "Do not send a human to do a machine's job"
> (c) Agent Smith
> 
> :)

Hey,

I proposed that a while ago already. I think the problem was Kate's 
distinction between global properties and "non-global" properties (e.g. ones 
that might get overwritten by modelines and such) -- afair.

KConfigXT doesn't really provide infrastructure (speak: API) for having this 
kind of cascading config settings.

Greets

-- 
Kevin Funk
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]