Hi,
I got a usecase where I had implemented in Qt4.8.x app on the assumption that
slots execute one after another in the order they are connected.
HMI response is slow when continuous data is pumped into my application from
other device.
Though we maintain separate threads(threads
Hi,
The order of the slots execution is undefined. You can not rely on it.
Bo.
Den 08-08-2014 10:39, Ramakanthreddy Kesireddy skrev:
Hi,
I got a usecase where I had implemented in Qt4.8.x app on the assumption
that slots execute one after another in the order they are connected.
HMI
Il 08/08/2014 10:51, Bo Thorsen ha scritto:
The order of the slots execution is undefined. You can not rely on it.
Generally speaking it *is* defined: slot activation follows the order of
the connect() statements (*).
In this specific case, there are multiple threads in the game, and the
Den 08-08-2014 12:15, Giuseppe D'Angelo skrev:
Il 08/08/2014 10:51, Bo Thorsen ha scritto:
The order of the slots execution is undefined. You can not rely on it.
Generally speaking it *is* defined: slot activation follows the order of
the connect() statements (*).
Yes.
In this specific
Am 08.08.2014 um 10:39 schrieb Ramakanthreddy Kesireddy
ramakanthreddy.kesire...@techmahindra.com:
...
If multiple signals are emitted once, I would like to know if framework would
take care of slots execution in parallel or in sequential order.
For direct connections slots are always
Am 08.08.2014 um 12:15 schrieb Giuseppe D'Angelo giuseppe.dang...@kdab.com:
Il 08/08/2014 10:51, Bo Thorsen ha scritto:
The order of the slots execution is undefined. You can not rely on it.
Generally speaking it *is* defined: slot activation follows the order of the
connect() statements
Den 08-08-2014 14:03, Till Oliver Knoll skrev:
Am 08.08.2014 um 12:15 schrieb Giuseppe D'Angelo giuseppe.dang...@kdab.com:
Il 08/08/2014 10:51, Bo Thorsen ha scritto:
The order of the slots execution is undefined. You can not rely on it.
Generally speaking it *is* defined: slot activation
