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

List:       koffice-devel
Subject:    Re: Use of processEvents()
From:       David Faure <faure () kde ! org>
Date:       2006-02-10 9:41:43
Message-ID: 200602101041.43484.faure () kde ! org
[Download RAW message or body]

On Thursday 09 February 2006 22:47, Giovanni Venturi wrote:> Alle 18:04, giovedì 09 \
febbraio 2006, David Faure ha scritto:> > On Thursday 09 February 2006 10:04, \
Jaroslaw Staniek wrote:> > > Hmm, in Kexi I am calling processEvents() from within a \
loop on data> > > loading in "data table view" destruction (both actions can a few \
seconds> > > or more) to make GUI more responsive. Both operations are isolated and> \
> > not GUI-related, just loading/destroying some data. Any risks?> >> > Yes, if you \
> > don't use a modal progress dialog while doing that, then the> > user could close \
> > the window, and assuming it is deleted and not just> > leaked, your code will be \
> > running inside a deleted object. Boom.>> Mmm, David I remember a talk of you and \
> > Till Adam in Malaga where you sayed > that better avoid processEvents() if I \
> > remember correctly
Yes, as I just said twice in this thread already :)
> This member is not thread-safe and can bring a crash of the application, can't?
?? This isn't about thread safety at all (in Qt3 all event processing happens inthe \
main thread only, and even in Qt4 there can be only one GUI thread).This is about \
                handling user input in the middle of a method, which is dangerous.
-- David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,Konqueror \
(http://www.konqueror.org), and KOffice (http://www.koffice.org). \
_______________________________________________koffice-devel mailing \
listkoffice-devel@kde.orghttps://mail.kde.org/mailman/listinfo/koffice-devel


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