Linked by Thom Holwerda on Tue 18th Jan 2011 22:18 UTC, submitted by alinandrei
Thread beginning with comment 459108
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
More News »
Sponsored Links



Member since:
2005-09-08
One thing they will realize is that QSettings is best used for application specific settings. Sharing settings between applications and especially between specific application is something it does extremely poorly. It is not something it is designed for, so I suspect they will find that while QSettings can use dconf, QSettings can not be used in place of dconf.
I have had this problem several time developing small GUI tools for internal use, QSettings is easy to use, but it is best used for application specific settings. When I wanted several small tools to share some of the same settings I had to do a lot of tricks to make it work in QSettings (basically reducing it to an ini-file parser).