summaryrefslogtreecommitdiffstats
path: root/src/corelib/statemachine/qstatemachine.h
Commit message (Collapse)AuthorAgeFilesLines
* kill the QT_STATEMACHINE_SOLUTION defineKent Hansen2009-05-131-8/+1
| | | | We won't release another Qt Solution, so the define is no longer needed.
* add QStateMachine::isRunning()Kent Hansen2009-05-071-0/+2
|
* Rename NoDefaultStateInHistoryState -> NoDefaultStateInHistoryStateError for ↵Eskil Abrahamsen Blomfeldt2009-05-071-1/+1
| | | | | | consistency The other error values have Error in the name for namespacing purposes.
* Fix infinite loop when source and target of transition are in different treesEskil Abrahamsen Blomfeldt2009-05-071-0/+1
| | | | | | | | | | | The SCXML algorithm depends on the guarantee that there is always an LCA regardless of the state list. The case where the targets are in a different tree than the source (e.g. if you have not given the target state a parent) is a bug. The fix is to set an error when this happens in exitStates() and exit states as if the pending error states were the target states. In enterStates we will detect the error and skip the step of selecting states to enter, and instead just enter the pending error states. This breaks transitions to and from the root state, which is not supported by the SCXML algorithm.
* kill QStateMachine::animationsFinished(), introduce QState::polished()Kent Hansen2009-04-291-4/+0
|
* kill QStateMachine::states() and QState::transitions()Kent Hansen2009-04-291-1/+0
| | | | Result of API review. Don't need them (for now).
* kill source/target-specific animationsKent Hansen2009-04-291-8/+0
| | | | | Result of API review. We don't have use cases for them yet. We can add them back if valid use cases do turn up.
* add animationsEnabled propertyKent Hansen2009-04-291-0/+6
|
* Remove API for setting specific restore policies on states. We have no clearEskil Abrahamsen Blomfeldt2009-04-231-2/+8
| | | | | | use case for this, so it has been removed. If the requirement arises we can add it back in later. Since it no longer makes sense to have it in QAbstractState, the RestorePolicy enum has been moved to QStateMachine.
* kill the stateactions apiKent Hansen2009-04-221-2/+2
| | | | | | | | | | | | It just didn't give us that much. Typically you just reimplement onEntry/onExit/onTransition when you want to do something. We go back to the signals-and-slots approach: states have entered() and exited() signals that you can connect to. It's still possible to have an action-based API, but then you build it on top of the core API, which is OK. Replacing 4 public classes (and one layer in the hierarchy) with 2 signals feels good.
* Add API for adding default animations to the state machine. This is especiallyEskil Abrahamsen Blomfeldt2009-04-211-0/+16
| | | | | | | useful when using the RestoreProperties policy, because this is intended to allow you to build a state machine without having each state consider all the possible properties that may be set by some state at some point. Default animations provide the same convenience for animated properties.
* Initial import of statemachine branch from the old kinetic repositoryAlexis Menard2009-04-171-0/+155
generated by cgit v0.12 at 2024-12-26 09:00:31 (GMT)