[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Re: Help: Reasons for signals not being delivered
From:       Sebastian =?iso-8859-1?q?Tr=FCg?= <trueg () kde ! org>
Date:       2009-06-09 17:39:32
Message-ID: 200906091939.32807.trueg () kde ! org
[Download RAW message or body]

On Tuesday 09 June 2009 17:24:11 Andreas Pakulat wrote:
> On 09.06.09 15:18:43, Sebastian Trüg wrote:
> > Hello,
> >
> > I am having a weird problem in K3b. In certain situations a signal from
> > QProcess is not delivered. I never block signals, I do not disconnect the
> > signals. What could be the reason?
> > Did you ever run into problems with signals not being delivered? Maybe
> > you just have random ideas I can test. I am a bit lost here.
> >
> > If you want details:
> > it is the QProcess::finished signal which is emitted by the
> > K3b::IsoImager process in k3bisoimager.cpp. Weirdly if only an image is
> > created (no cdrecord process is started) the signal is delivered. I
> > simply cannot find the reason. Well, maybe I do as soon as I send this
> > email, wouldn't be the first time. ;)
>
> Well, one thing that comes to mind is that finished is only delivered if
> the process could actually be started. If a process cannot be started for
> some reason then QProcess will only emit the error() signal. You could also
> use waitForStarted() after start() to make sure that your process has been
> started properly.

thanks for the hint. However, the process is started, it even finishes 
successfully (the image is created via mkisofs). I even debugged into the code 
in QProcess with a breakpoint and actually made sure the signal is emitted. 
Only the connected slot is not called (and it is a direct unqueued connection)
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]