Dataengnies

[Petri Damstén]

On Wednesday 27 August 2008 20:04:11 Aaron J. Seigo wrote:
> actually, scratch that. checkForUpdate is better than doing it manually;
> the issue is *probably* that the signal/slot connections haven't been made
> yet.
>
> it's not safe to start an update from the constructor due to this. so .....
> you can do one of two things:
>
> * call ExecutableContainer::exec() from the engine right after it is
> created
>
> * QTimer::singleShot(0, this, SLOT(exec())); inside the ExecutableContainer
> ctor
>
> the first option is probably the safest, however.

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.

Petri

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20080827/541269eb/attachment.sig