diff options
| author | Kent Hansen <khansen@trolltech.com> | 2009-04-22 15:20:19 (GMT) |
|---|---|---|
| committer | Kent Hansen <khansen@trolltech.com> | 2009-04-22 15:20:19 (GMT) |
| commit | f87641584424deed25e2abdadea08c3be94b9ce1 (patch) | |
| tree | a185687744e724a8db896970416f23d20f5cad38 /examples/animation/states/akregator.png | |
| parent | 31f5348ea1691a7664b6abc04cf425dd02637b33 (diff) | |
| download | Qt-f87641584424deed25e2abdadea08c3be94b9ce1.zip Qt-f87641584424deed25e2abdadea08c3be94b9ce1.tar.gz Qt-f87641584424deed25e2abdadea08c3be94b9ce1.tar.bz2 | |
kill the stateactions api
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.
Diffstat (limited to 'examples/animation/states/akregator.png')
0 files changed, 0 insertions, 0 deletions