On Wednesday, January 27, 2016 10:32:50 AM EST Boudewijn Rempt wrote:
> On Sat, 23 Jan 2016, David Faure wrote:
> > (I don't mean "it's called KConfig" ;-) I mean what does the code using
> > it, look like? I think this needs some debugging to find out where this
> > "local" string comes from)
> Well, it's done in a lot of places, about 160, like:
>
> KConfigGroup cfg =
> KSharedConfig::openConfig()->group("advancedColorSelector");
>
> or
>
> KConfigGroup cg(KSharedConfig::openConfig(), "");
>
>
> What I want in the end is have AppData\Roaming\Krita\ where both kritarc and
> the user's custom resources are saved, like brushes and so on. I'm fine
> with patching kconfig for windows for that, though.
Won't this change the behaviour from Unix like systems? They won't have the
Krita folder in the name, so they will just get dumped in the common config
folder. I don't think carrying a patch like that for KConfig is a good idea.
--
Matthew
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
