Timeline for How to wire finite state machine into component-based architecture?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 10, 2012 at 2:58 | comment | added | Sean Middleditch | @Pup: From a code perspective, as I built it, a Behavior is an Action. From a conceptual point, Actions are usually transitory -- they exist only until "complete" -- while Behaviors are forever and never get removed from the list. I've seen another team build a similar system but with two lists, one for Actions and one for Behaviors, which works well enough. I like having the ability for an Action to block certain behaviors, though, using the bitmasks and grouping (lanes, I believe I called them in the slides). Sorry that middle slide's graphic is so bad. :) | |
| S Apr 9, 2012 at 15:51 | history | suggested | Pup | CC BY-SA 3.0 | Added images from slideshow |
| Apr 9, 2012 at 14:23 | comment | added | Pup | What's the fundamental difference between "Behaviors" and "Actions"? | |
| Apr 9, 2012 at 14:20 | vote | accept | Pup | ||
| Apr 9, 2012 at 14:20 | review | Suggested edits | |||
| S Apr 9, 2012 at 15:51 | |||||
| Apr 8, 2012 at 11:27 | history | answered | Sean Middleditch | CC BY-SA 3.0 |