Page MenuHomePhorge

Port to KConfigXT
ClosedPublic

Authored by nannanko on Sat, Aug 8, 12:46 PM.
Tags
None
Referenced Files
F85651328: D346.1788051423.diff
Fri, Aug 28, 5:57 PM
F85651294: D346.1788047068.diff
Fri, Aug 28, 4:44 PM
F85651201: D346.1788035076.diff
Fri, Aug 28, 1:24 PM
F85651123: D346.1788032062.diff
Fri, Aug 28, 12:34 PM
Subscribers
None

Details

Summary

Port to KConfigXT

Type: add

Test Plan

Compile and open kazv, verify that all config are correct.

Veridy unit tests pass.

Diff Detail

Repository
rK kazv
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

tusooa requested changes to this revision.Thu, Aug 13, 7:40 PM
tusooa added inline comments.
src/kazv-settings.kcfg
7

Is it possible to use QStandardPaths::AppConfigLocation instead of hard-coding a directory?

This revision now requires changes to proceed.Thu, Aug 13, 7:40 PM
src/kazv-settings.kcfg
7

Is it possible to use QStandardPaths::AppConfigLocation instead of hard-coding a directory?

The constructor of KConfigXT is fixed to GeneralConfigLocation, it seems there is no official support.

src/kazv-settings.kcfg
7

https://api.kde.org/kconfigcompiler.html

The <kcfgfile> tag may contain either the "name" attribute, which should be the name of the configuration file described, or the "arg" attribute, which, if set to "true", will allow you to pass the KSharedConfig::Ptr object to use.

Port to AppConfigLocation.

This revision is now accepted and ready to land.Wed, Aug 19, 11:57 AM
This revision was landed with ongoing or failed builds.Sat, Aug 22, 4:37 AM
This revision was automatically updated to reflect the committed changes.