Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | compile after api changes | Kent Hansen | 2009-04-28 | 1 | -4/+4 |
| | |||||
* | kill the stateactions api | Kent Hansen | 2009-04-22 | 1 | -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. | ||||
* | Initial import of statemachine branch from the old kinetic repository | Alexis Menard | 2009-04-17 | 2 | -0/+204 |