Closed neapel closed 10 years ago
I'm actually in the process of making actions associated with inputs rather than states, this was an oversight in my original implementation. A new release with these changes (and labeling of actions in the view
diagrams) will be forthcoming soon.
I've been poking at this a bit while on vacation. With the new commit, you'll get a visualization that looks like:
Can you confirm this is the desired behavior?
Yes, that's great!
Could you add more details on when the reduce actions are being executed to the documentation, and show the actions in the
view
graph?In the documentation it reads like the actions might be associated with the transitions, but they actually seem to be collected on each state, i.e. for
:x :w
input action:F
is still executed because it's associated with state 1, not the transition:z
.