Well we have 3 different ways and priorities to set the config file. One of the possibilities is: We have a default config file which uses a hardcoded filename but the path to this file is created with the default config file path + organization name + application name. For detailed information please visit: http://codereview.qt-project.org/13226
B.R. WB -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Thiago Macieira Sent: Tuesday, February 21, 2012 3:18 AM To: [email protected] Subject: Re: [Development] QLog ( Work on qDebug and friends) On segunda-feira, 20 de fevereiro de 2012 16.42.00, David Faure wrote: > > Clearly you haven't read > > http://codereview.qt-project.org/#change,13226 > > > > > > > > > We've removed all traces of > > > QSettings support so QSettings could be moved away. > > QFile is all that's needed to implement a basic config file, QSettings > is not needed. No, I haven't looked at the patch yet. (Take a look at my dashboard to see why) Let QLog have a function that allows one to externally enable and disable categories. If you really want to, provide a way to parse config data via QFile, like you suggested. But please don't hardcode any file names inside the library. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center Intel Sweden AB - Registration Number: 556189-6027 Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
