[Interest] QSettings watching for updates.

[Jason H]

Yes, but that would not be portable. However you can force QSettings to use another storage medium. (i.e. a file) which would be portable and transparent.



________________________________
 From: Scott Aron Bloom <Scott.Bloom at onshorecs.com>
To: Jason H <scorp1us at yahoo.com>; Till Oliver Knoll <till.oliver.knoll at gmail.com>; interest at qt-project.org 
Sent: Monday, January 23, 2012 3:01 PM
Subject: RE: [Interest] QSettings watching for updates.
 

Hoever, it would NOT be hard to extend FileSystemWatcher to handle watching the registry.

Similar Win32 messages are emitted when the portion of the registry changes and you are watching that portion..

Scott
 
 
 
From:interest-bounces+scott.bloom=onshorecs.com at qt-project.org [mailto:interest-bounces+scott.bloom=onshorecs.com at qt-project.org] On Behalf Of Jason H
Sent: Monday, January 23, 2012 11:54 AM
To: Till Oliver Knoll; interest at qt-project.org
Subject: Re: [Interest] QSettings watching for updates.
 
I'd just suggest the QFileSystem watcher with a file (won't work with Windows registry QSettings)
 
 

________________________________

From:Till Oliver Knoll <till.oliver.knoll at gmail.com>
To: "interest at qt-project.org" <interest at qt-project.org> 
Sent: Monday, January 23, 2012 6:18 AM
Subject: Re: [Interest] QSettings watching for updates.



Am 21.01.2012 um 15:32 schrieb Alan Ezust <alan.ezust at gmail.com>:

> Qt Mobility has a publish-subscribe module which is basically like QSettings but with IPC in mind.
> It already has the ability to notify you of changes.

If "immediate notifications" are not a must, then "polling for changes" might also be a possibility: re-loading the QSettings every n minutes (or seconds).

Cheers, Oliver
_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20120123/8cc1b333/attachment.html>