On Wednesday, 13 November 2019 09:16:13 PST Benjamin TERRIER wrote:
> I guess unless we change QClipboard API to make it async (like in GTK) I do
> not see how to solve this issue.
I think adding the async API and deprecating the current is the right way to
go. The two APIs need to work together,
Le mar. 5 nov. 2019 à 17:39, Thiago Macieira a
écrit :
>
> Probably *because* events would be processed during the wait. We all know
> nested event loops are bad design. In this case, this stems from another
> bad
> API design: the clipboard handled synchronously, when it clearly isn't.
>
> Note:
HI everyone,
We have released Qt 5.12.6 today, see https://www.qt.io/blog/qt-5.12.6-released
Big thanks to everyone involved!
br,
Jani
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Am 11.11.19 um 18:13 schrieb Jason H:
> If not Javascript, then what? Python? This is the first I've heard of
> this. Just wondering what it is if not javascript?
This is a little tricky to answer just in email text. But what I think I
can do safely is show you two snippets of code from our ex
Hi,
I see that all the presentations from last year's World Summit have become
available as recordings for viewing on Youtube at
https://www.youtube.com/QtStudios . I'm cautiously optimistic that this year's
presentations will become available as well. I can't promise it though, but I'm
crossi
01.11.2019, 17:08, "Konstantin Tokarev" :
> 01.11.2019, 16:38, "Heikki Halmet" :
>> Hi,
>>
>> We don't know the exact date yet. It depends when we get fixes for
>> https://bugreports.qt.io/browse/QTBUG-79623 or we need to make some kind of
>> workaround for the patches we have in master branc
Hi,
'5.13' branch will be closed soon; immediately after '5.14.0' is created.
'5.13' will be merged to '5.14' before final downmerge from '5.14' to '5.14.0'
so Qt 5.14.0 release will have all fixes from '5.13'.
After '5.13' is closed all fixes should be targeted to '5.14' by default.
br,
Jani
