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
>
> From what you've shown, it may be that you can rely on the *reverse* order.
I can't, since I'm receiving the opposite results on my local machine.
My local machine accepts the intuitive order of timeouts (quite fast one),
while the CI doesn't.
Best regards
Jarek
___
[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
On Monday, 29 May 2023 11:40:14 PDT Jaroslaw Kobus via Development wrote:
> Hi All,
>
> when I start 2 single shot timers synchronously in a row, with exactly the
> same interval, from the same thread, can I rely on having their handlers
> called in the same order in which they were started?
>
>
Hi All,
when I start 2 single shot timers synchronously in a row, with exactly the same
interval, from the same thread, can I rely on having their handlers called in
the same order in which they were started?
I.e.:
QTimer::singleShot(1000, [] { qDebug() << "1st timer elapsed"; });
