| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
...hopefully
|
|
|
|
| |
Reviewed-by: Trust Me
|
| |
|
| |
|
|
|
|
|
| |
We decided to remove the const of the eventTest() since some transitions
have dynamic conditions and need to update when eventTest() is called.
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
Conflicts:
examples/animation/sub-attaq/states.cpp
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Result of API review. A == comparison of the modifiers is not useful.
The common case is you want to test if one or more modifiers are set,
i.e. a mask check.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/ |
|
| |
|
| |
|
|
|
|
| |
sub-attaq doesn't use anymore animation private headers
|
| |
|
|
|