summaryrefslogtreecommitdiffstats
path: root/src/corelib/statemachine/qstate.h
Commit message (Collapse)AuthorAgeFilesLines
* Update license headers in files that are new in 4.6.Jason McDonald2009-06-171-2/+2
| | | | Reviewed-by: Trust Me
* add QT_NO_STATEMACHINE define so state machine can be compiled outKent Hansen2009-06-041-0/+4
| | | | Reviewed-by: Thierry Bastian
* kill the QT_STATEMACHINE_SOLUTION defineKent Hansen2009-05-131-4/+0
| | | | We won't release another Qt Solution, so the define is no longer needed.
* add event as argument to onEntry(), onExit() and onTransition()Kent Hansen2009-05-051-2/+2
| | | | | | | | | Accessing the event can be useful. E.g., onEntry() can do some common event processing regardless of which transition caused the state to be entered; onTransition() can be used in combination with eventTest(), where eventTest() would first check that the input matches some criteria, and then the actual processing of that input would be done in onTransition.
* kill QStateMachine::states() and QState::transitions()Kent Hansen2009-04-291-1/+0
| | | | Result of API review. Don't need them (for now).
* replace QState::Type with QState::childMode propertyKent Hansen2009-04-291-5/+11
| | | | Result of API review.
* make history state constructibleKent Hansen2009-04-291-7/+0
| | | | | | | | | | | Decided in API review. The intention of QHistoryState not being constructible was so that people wouldn't subclass it and reimplement onEntry()/onExit(), thinking that those functions would actually get called (which they won't). However, we recently added the entered() signal to QAbstractState, so people are going to connect to it and ask why they never get the signal for a QHistoryState. We might as well make QHistoryState constructible and just document that it doesn't make sense to subclass it.
* move assignProperty() to QStateKent Hansen2009-04-291-0/+4
| | | | Doesn't belong in the abstract base class.
* replace QStateFinished{Event,Transition} by QState::finished() signalKent Hansen2009-04-271-2/+3
| | | | | Not worth it having two public classes when the same can be achieved by having a signal.
* kill the stateactions apiKent Hansen2009-04-221-3/+3
| | | | | | | | | | | | 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.
* Have QState::addTransition(QAbstractTransition*) return the transition objectEskil Abrahamsen Blomfeldt2009-04-211-1/+1
| | | | | | | | | when it is added. Reduces the number of temporary variables you have to declare in your code since you can do things like: state->addTransition(new Transition())->addAnimation(new Animation()); Could also be used for error checking.
* Initial import of statemachine branch from the old kinetic repositoryAlexis Menard2009-04-171-0/+114
generated by cgit v0.12 at 2024-10-22 15:27:23 (GMT)