On Tuesday, 30 May 2023 17:10:11 PDT Ilya Fedin wrote:
> On Tue, 30 May 2023 16:55:51 -0700
>
> Thiago Macieira wrote:
> > After trying myself, it turns out the problem is not QTimer or the
> >
> > event dispatcher, but the Windows API. The following test:
> >
On Tue, 30 May 2023 16:55:51 -0700
Thiago Macieira wrote:
> After trying myself, it turns out the problem is not QTimer or the
> event dispatcher, but the Windows API. The following test:
> https://codereview.qt-project.org/c/qt/qtbase/+/480705
> passes on Linux (glib and native), macOS but
On Tuesday, 30 May 2023 15:52:48 PDT Jaroslaw Kobus via Development wrote:
> I don't know QTimer's internals, so I can't comment on this. However, please
> refer to what the CI machine reports for:
> https://codereview.qt-project.org/c/qt-creator/qt-creator/+/480663/1
After trying myself, it
> On Tuesday, 30 May 2023 12:25:10 PDT Jaroslaw Kobus wrote:
> > Hi Thiago,
> >
> > thank you for your answer. There are 3 main points:
> >
> > 1. Coarsing is OK and I'm totally fine with having my timers called a bit
> > earlier or later (within 5% accuracy).
> >
> > However, this doesn't explain
[Re-sending my reply to Thiago to the mailing list, as I think it may be
possibly interesting for more people.]
[In meantime I've created
https://codereview.qt-project.org/c/qt/qtbase/+/480703 and waiting for CI
results.]
> On Monday, 29 May 2023 11:40:14 PDT Jaroslaw Kobus via Development
When running lupdate from a yocto sdk, I get the following error:
$ lupdate -pro example.pro
sh: 1: /usr/libexec/lupdate-pro: not found
qt.conf:
[Paths]
Prefix = /usr
Headers = /usr/include
Libraries = /usr/lib64
ArchData = /usr/lib64
Data = /usr/share
Binaries = /usr/bin
LibraryExecutables =
+1!
Doris
From: Development on behalf of Axel Spoerl
via Development
Date: Monday, 29 May 2023, 10:50 PM
To: Qt development mailing list
Subject: Re: [Development] Nominating Artem Dyomin as Approver
+1
Von: Development im Auftrag von Lars Knoll
Gesendet:
