Using QApplication::processEvents

[Hamish Rodda]

On Wednesday 03 May 2006 15:30, Vladimir Prus wrote:
> On Wednesday 03 May 2006 01:00, Alexander Neundorf wrote:
> > On Tuesday 02 May 2006 21:58, Andras Mantia wrote:
> > > On Tuesday 02 May 2006 18:19, Jens Dagerbo wrote:
> > > > There are still a few of them left and I have on my todo to remove a
> > > > few more of them.. please don't add more of them.
> > >
> > > I agree, please don't do it. Use timers (singleshot) or whatever, but
> > > not processEvents. And if you really want to use it, use should use
> > > ExcludeUserInput and ExcludeSocketNotifiers. But better don't use it at
> > > all.
> >
> > Same here, processEvents() is *evil*.
> > Caused also a major bug in kfind.
> > Don't use it.
>
> Ok, then I'll either try to use threads, or wait till port to Qt4 (where
> threads should be much nicer to work with).

I agree with the above, processEvents() is definitely the wrong solution, so 
you've got the right idea.

Qt4 will be much better, to the point where I think you can have the model in 
the debugger thread and plug it into the view in the gui thread, thus not 
having to do much to cross threads anyway :)

Cheers,
Hamish.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20060503/5142223c/attachment.sig>