Change State Machine to use callbacks and an execute() function

[rbmj]

To diversify the code base and to avoid having giant functions, can we move all of the code logic to some callbacks that are registered with the state? The two easiest ways to do this are with the state_machine type construct in hex43 and the registry. I don't care how you do it, but we need to make this easy and extensible. I see state machines running inside of state machines... :)

[anidev]

Blair, in thought of using your state machine, but that works by calling different functions from triggers based on state, and the way our code is written right now, we don't really have triggers to process. I thought that something simple to keep track of state between continuous calls would suffice, so we created state_tracker.

Unless we change joysmooth to process triggers like a finite state machine, I don't know if we need a true state machine or not. I was, however, originally planning to move the different functions for different states into separate functions, out of main, and having a callback registry, something like a c++ equivalent of java hashmaps, that will call the appropriate callback.

Sent from my Android device.

-----Original Message-----
From: "Robert Blair Mason Jr." reply@reply.github.com
To: Anirudh B anidev.aelico@gmail.com
Sent: Mon, 06 Feb 2012 5:44 PM
Subject: [612-code] Change State Machine to use callbacks and an execute() function (#23)

To diversify the code base and to avoid having giant functions, can we move all of the code logic to some callbacks that are registered with the state? The two easiest ways to do this are with the state_machine type construct in hex43 and the registry. I don't care how you do it, but we need to make this easy and extensible. I see state machines running inside of state machines... :)

---

Reply to this email directly or view it on GitHub:
#23