Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
5.12.4, 5.14.2, 5.15.7, 6.2.1
-
-
8
-
50815b095f (qt/qtscxml/dev) 50815b095f (qt/tqtc-qtscxml/dev) c42f20dae2 (qt/qtscxml/6.4) c42f20dae2 (qt/qtscxml/6.4.1) c42f20dae2 (qt/tqtc-qtscxml/6.4) c42f20dae2 (qt/tqtc-qtscxml/6.4.1) 0dc7c2878b (qt/tqtc-qtscxml/6.2) 29c25449e7 (qt/tqtc-qtscxml/5.15)
-
Foundation Sprint 68, Foundation Sprint 69
Description
The properties of a scxml state machine seem to be broken if "History" is added to the .scxml chart. Submitting an event to the state machine results in a correct state change. There are property changes as well like expected but the property values don't match the active states at all. The property values are initially correct.
Steps to reproduce:
- Run the attached project
- Click on "S01 => S1" to change state from S0 to S1 & monitor the output
(as a result the state machine logs "S1" as active state but the S1 property remains false. This does not occur if history (History_1) is removed from the .scxml chart)
Attachments
Issue Links
- is duplicated by
-
QTBUG-86626 Adding History state breaks state chart
- Closed
- mentioned in
-
Page Loading...