On July 14, 2010, Thomas Fjellstrom wrote: > > one way around that is to not use the setData API in DataEngine, but to > > instead create subclasses of DataContainer for each sourc. when all the > > data is retreived, then the DataContainer can call checkForUpdate(). > > that should work better for your use case. > > Hmm, so after I receive the updates from QHostInfo/QProcess, I should call > checkForUpdate in my new custom DataContainer?
right. > > > > > 2. DataEngine::setPollingInterval seems to poll only once. > > > > > > > > yes, that's an engine-wide polling interval. > > > > > > I mean once period. I expected it to actually setup a regular poll, not > > > a one shot timer. > > > > that was a bug; i've just fixed it. it now does set up a regular poll as > > it is supposed to :) > > Will the fix make it into 4.5? yes, i backported it. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel