KConfig compiler. GenerateProperties and Mutable.

[David Faure]

On jeudi 26 mai 2016 02:31:29 CEST Artem Fedoskin wrote:
> >>> We could also start with turning that into quint64, to already double
> 
> the number of possible settings, right? Easy short term fix.
> 
> Am I correct that with quint64 we will gain just 32 more additional unique
> signal bit masks? The problem is that my config file has more than 300.

Oh, OK.

> I managed to make mSettingsChanged QHash<int,bool>. This way we hold there
> only non-modify signals. However, I encountered some other problems:
> 
>    1. Sometimes read function in Q_PROPERTY declaration starts with capital
>    letter while the read function itself starts with the lowercase one.
> Almost the same thing happens with signal names. At each call to
>    changeSignalName() and name() I make the first letter capital, is it OK?

I'm afraid I don't understand what you mean (I don't know the kconfig_compiler 
code that well). First letter uppercase is very unusual though, for anything
except class names and enums.

>    2. Some of the properties in my .kcfg file have min and max values but
>    KConfigCompilerSignallingItem doesn't support them. Should I just copy
> all the stuff from ItemInt or is it better to make it a subclass of
> ItemInt?

No idea, sorry.

CC'ing the kconfig maintainer.

-- 
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5