On Thursday, 8 October 2020 14:33:59 PDT Philippe wrote:
> > > Thiago Macieira wrote:
> > If nothing is signaled, why are they waking up at all?
>
> Let me rephrase otherwise:
> if one calls WaitForSingleObject or WaitForMultipleObjects
> with a timeout of 1 millisecond, then these functions
>
Il 08/10/20 23:33, Philippe ha scritto:
Let me rephrase otherwise:
if one calls WaitForSingleObject or WaitForMultipleObjects
with a timeout of 1 millisecond, then these functions
won't return before 15 milliseconds (provided the events don't get
signaled during that period).
But what would
> > Thiago Macieira wrote:
> If nothing is signaled, why are they waking up at all?
Let me rephrase otherwise:
if one calls WaitForSingleObject or WaitForMultipleObjects
with a timeout of 1 millisecond, then these functions
won't return before 15 milliseconds (provided the events don't get
On Thursday, 8 October 2020 02:00:13 PDT Konstantin Tokarev wrote:
> Is resolution of QElapsedTimer limited to 15 ms as well? If it's more find
> grained you can try busy-waiting until required time elapses.
Any such submission to Qt will get an immediate -2 from me. If you really need
it, you
On Thursday, 8 October 2020 01:43:38 PDT Philippe wrote:
> On Wed, 7 Oct 2020 17:34:43 -0700
>
> Thiago Macieira wrote:
> > Now, the question is how WaitFor{SingleObject,MultipleObjects} are
> > affected. Does this mean that asking for a timeout of 2 milliseconds
> > could result in being 13
Hi everyone!
I am happy to announce that Qt Automotive Suite 5.15.1 has been released.
Check the blog post for more details,
https://www.qt.io/blog/qt-automotive-suite-5.15.1-released
Big thanks to everyone involved!
br,
Jukka Jokiniva
Release Manager
The Qt Company
If you subclass QQuickItem and start handling events, it becomes clear that
QEvent::accept() has always meant two things in legacy Qt Quick: 1) stop
propagation and 2) grab the mouse. (Does this idea bother you yet?)
The item is basically saying “the buck stops here”: it’s so very sure that no
08.10.2020, 11:59, "Toni Saario" :
>>> Most of provisioning scripts fall into 2 categories:
>>> 1) Download installer (or other binary package) of 3rd party stuff, verify
>>> checksum, install. These scripts are quite simple.
>>> 2) Build stuff from sources in provisioning time, sometimes in a
08.10.2020, 11:46, "Philippe" :
> On Wed, 7 Oct 2020 17:34:43 -0700
> Thiago Macieira wrote:
>
>> Now, the question is how WaitFor{SingleObject,MultipleObjects} are affected.
>> Does this mean that asking for a timeout of 2 milliseconds could result in
>> being 13 seconds too late?
>
> I
> Most of provisioning scripts fall into 2 categories:
> 1) Download installer (or other binary package) of 3rd party stuff, verify
> checksum, install. These scripts are quite simple.
> 2) Build stuff from sources in provisioning time, sometimes in a
> sophisticated way (e.g.
>
On Wed, 7 Oct 2020 17:34:43 -0700
Thiago Macieira wrote:
> Now, the question is how WaitFor{SingleObject,MultipleObjects} are affected.
> Does this mean that asking for a timeout of 2 milliseconds could result in
> being 13 seconds too late?
I just did a test, and yes, both
Il 08/10/20 02:34, Thiago Macieira ha scritto:
Now, the question is how WaitFor{SingleObject,MultipleObjects} are affected.
Does this mean that asking for a timeout of 2 milliseconds could result in
being 13 seconds too late?
I hope you meant *milli*seconds...
But anyhow, WaitForX allow for
12 matches
Mail list logo
