On Tuesday, 25 June 2019 23:58:53 PDT Fabrice Mousset | GEOCEPT GmbH wrote:
> I will have to rework the whole process.
> I have a worker class (with his own thread), and before allowing a new task
> to be started I have to be sure previous task has been finished.
Yes, you will have to rework
Can't you use a QRunnable / QThreadPool with maxThreadCount=1?
> Sent: Wednesday, June 26, 2019 at 1:58 AM
> From: "Fabrice Mousset | GEOCEPT GmbH"
> To: "Thiago Macieira" , "interest@qt-project.org"
>
> Subject: Re: [Interest] QEventLoop ::
> -Ursprüngliche Nachricht-
> Von: Interest Im Auftrag von Thiago
> Macieira
> Gesendet: Dienstag, 25. Juni 2019 18:09
> An: interest@qt-project.org
> Betreff: Re: [Interest] QEventLoop ::hasPendingEvents() replacement?
>
> On Tuesday, 25 June 2019 08:00:02 PDT Fabrice Mousse
On Tuesday, 25 June 2019 08:00:02 PDT Fabrice Mousset | GEOCEPT GmbH wrote:
> Hi all,
>
> Since Qt 5.3 QAbstractEventDispatcher::hasPendingEvents() has been set
> "obsolete". Is there an alternate way to know if a QEventLoop has pending
> events?
The reason it's obsolete is that it's a race
Hi all,
Since Qt 5.3 QAbstractEventDispatcher::hasPendingEvents() has been set
"obsolete".
Is there an alternate way to know if a QEventLoop has pending events?
Best regards
Fabrice Mousset
___
Interest mailing list
Interest@qt-project.org
