[Development] QSettings refactor updates

Thiago Macieira thiago.macieira at intel.com
Mon Oct 13 14:41:08 CEST 2014

On Monday 13 October 2014 13:47:44 André Somers wrote:
> Thiago Macieira schreef op 11-10-2014 10:25:
> > On Friday 10 October 2014 21:27:58 Tomaz Canabrava wrote:
> >> I tougth about having a changed() signal on the QConfig / QConfigGroup
> >> classes, is the QConfigWatcher a better approach?
> > 
> > Put it in a separate class. QConfig (Group) should not be a QObject.
> Why not?

QConfigGroup definitely cannot be a QObject. QObjects can't be copied, so we 
can't do the value semantics we asked for. Those are conflicting design 

Make it like the QDBusPendingReply + QDBusPendingCallWatcher or QFuture + 
QFutureWatcher pairs. We have the precedent there.
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Development mailing list