.
Feel free to make comments if you are interested.
Best regards,
Sona
From: Development On Behalf Of Sona
Kurazyan
Sent: Friday, 31 January 2020 17:24
To: development@qt-project.org
Subject: Re: [Development] Make a decision for asynchronous APIs
Hi everyone,
It's been a while since
ссаров mailto:abba...@gmail.com>>
Sent: Saturday, February 1, 2020 1:56 PM
To: Sona Kurazyan mailto:sona.kuraz...@qt.io>>
Cc: development@qt-project.org<mailto:development@qt-project.org>
Subject: Re: [Development] Make a decision for asynchronous APIs
Can you please elaborate the diffe
0 1:56 PM
> To: Sona Kurazyan
> Cc: development@qt-project.org
> Subject: Re: [Development] Make a decision for asynchronous APIs
>
> Can you please elaborate the difference?
>
>
> 31 янв. 2020 г., в 17:24, Sona Kurazyan <mailto:sona.kuraz...@qt.io>> написал(а):
>
Den lör 1 feb. 2020 kl 14:48 skrev Sona Kurazyan :
>
>
>
> > -Original Message-
> > From: Elvis Stansvik
> > Sent: Friday, January 31, 2020 7:20 PM
> > To: Sona Kurazyan
> > Cc: development@qt-project.org
> > Subject: Re: [Devel
> -Original Message-
> From: Elvis Stansvik
> Sent: Friday, January 31, 2020 7:20 PM
> To: Sona Kurazyan
> Cc: development@qt-project.org
> Subject: Re: [Development] Make a decision for asynchronous APIs
>
> >
> > Additionally, there are some disc
: Иван Комиссаров
Sent: Saturday, February 1, 2020 1:56 PM
To: Sona Kurazyan
Cc: development@qt-project.org
Subject: Re: [Development] Make a decision for asynchronous APIs
Can you please elaborate the difference?
31 янв. 2020 г., в 17:24, Sona Kurazyan
mailto:sona.kuraz...@qt.io>> нап
ards,
Sona
> -Original Message-
> From: Allan Sandfeld Jensen
> Sent: Friday, January 31, 2020 7:40 PM
> To: development@qt-project.org
> Cc: Sona Kurazyan
> Subject: Re: [Development] Make a decision for asynchronous APIs
>
> On Freitag, 31. Januar 2020 17:24:20 CET Son
Can you please elaborate the difference?
> 31 янв. 2020 г., в 17:24, Sona Kurazyan написал(а):
>
> Additionally, there are some discussions about QFuture being a mix between a
> “Task” and a “Future”. One of the options of improving this situation is to
> make a QTask (or QJob) out of the cur
On Freitag, 31. Januar 2020 17:24:20 CET Sona Kurazyan wrote:
> Additionally, there are some discussions about QFuture being a mix between a
> “Task” and a “Future”. One of the options of improving this situation is to
> make a QTask (or QJob) out of the current QFuture. But then the question
> is:
cancel/pause/resume/progress API would be on QTask?
Elvis
>
>
>
> Please share your thoughts!
>
>
>
> Thanks,
>
> Sona
>
>
>
>
>
> From: Development on behalf of Karsten
> Heimrich
> Sent: Thursday, December 19
___
From: Development on behalf of Karsten
Heimrich
Sent: Thursday, December 19, 2019 2:12 PM
To: development@qt-project.org
Subject: [Development] Make a decision for asynchronous APIs
Hi,
we are planning to continue some work on the QFuture, QtConcurrent APIs, either
Hi,
we are planning to continue some work on the QFuture, QtConcurrent APIs, either
improve up on the existing implementation or deprecate and remove them
completely for Qt6. We've created a user story in Jira and like to gather some
feedback here. So if this topic is of interest for you, I wou
12 matches
Mail list logo
