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

List:       kde-devel
Subject:    Re: Help: Reasons for signals not being delivered
From:       Frank Osterfeld <frank.osterfeld () gmx ! de>
Date:       2009-06-09 19:01:34
Message-ID: 200906092101.34466.frank.osterfeld () gmx ! de
[Download RAW message or body]

On Tuesday 09 June 2009 07:40:30 pm Sebastian Trüg wrote:
> On Tuesday 09 June 2009 19:05:47 Frank Osterfeld wrote:
> > On Tuesday 09 June 2009 03:18:43 pm 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?
> >
> > Is the signal emitted at all? Try set a breakpoint there. I'd also go for
> > Andreas guess and check that error conditions are handled correctly. I
> > find the QProcess API a bit confusing there and it's easy to get it
> > wrong.
>
> I already did that. Signal is emitted. Only the connected slot it not
> called. And the connection is direct, not queued.

There are also several methods in the public Q_SLOTS which shouldn't be slots 
I think. I don't think that has an influence though.
I would also check that the moc is correctly generated and not confused by the 
several multiple baseclasses.

Frank
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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