Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.4.0
-
None
-
Qt 5.4.0
-
c6f0e3967992780e7786d6bdd90b21149009f2fd
Description
With qt 5.4 it is not possible to use the running property to deduce whether a timer can be safely assumed to not trigger (or whether it has already triggered), since timers that are not running are now sending the triggered signal. This seems like misuse of the running property, it should really be updated directly after the triggered signal is emitted.
This was probably introduced by the change in ca43c4121dde6c8f5d4eabfcf128ff6214996d54 (in relation to QTBUG-39371).
Attachments
For Gerrit Dashboard: QTBUG-44026 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
104176,3 | Fix QML Timer running not being updated together with triggered signal | 5.4 | qt/qtdeclarative | Status: MERGED | +2 | 0 |