Hi I recently got annoyed with the ConfigObject<ConfigValue> system a lot. I think it adds a lot of unnecessary complexity by having to pass it around in constructors a lot and not being thread safe.
Qt has a nice class for this called QSettings. You can get them where ever you want in the code supports QVariant as a value type. Changes will be effective immediately across all instances in the same process, while being threadsafe. We can also get the filepath to store our db analysis and everything else in the same location where QSettings stores all. http://qt-project.org/doc/qt-4.8/qsettings.html pros: * less code * thread safe * values are based on QVariant * no API change if we want the settings/config in a class * better platform integration * easy systemwide configuration I would like to change from ConfigObject to QSettings for 1.12. I will also add a blueprint soon for this and see how we can smoothly upgrade to QSettings. Are there any good reasons to keep our old system that I overlooked? best Max ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Get Mixxx, the #1 Free MP3 DJ Mixing software Today http://mixxx.org Mixxx-devel mailing list Mixxx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mixxx-devel
