Dataengnies

[Aaron J. Seigo]

On Wednesday 27 August 2008, Petri Damstén wrote:
> On Wednesday 27 August 2008 20:04:11 Aaron J. Seigo wrote:

> All three ways works the same way. Debug output in previous email shows
> that it goes like this:
> checkForUpdate() -> relay->checkQueueing() -> where m_queued == false and
> signal won't get emitted. It gets set to true only in timerEvent(?) which
> is not called yet.

ah, you're connecting using a timeout (which is a bit odd in this case, 
really; why would you want a regularly timed update from a command vs getting 
it's output when it arrives?)

in any case .. this is probably due to the change i made the other day that 
doesn't immediately schedule an update if it is the first item connected.

can you try the attached patch and see if that helps any?

-- 
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 Trolltech

-------------- next part --------------
A non-text attachment was scrubbed...
Name: relays_on_quick_change.cpp
Type: text/x-c++src
Size: 883 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20080827/51ca3c80/attachment.cpp 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20080827/51ca3c80/attachment.sig