Thought I would add my two cents on this sub-topic - I use string driven state machines instead of enum type defs when I want to create a scriptable state machine. That is, the state sequence is driven by a text file that has information about what order the states are executed. This means the test sequence can be modified in the field using any text editor. Clearly, this flexibility is not always required (or even advisable) but when it is, it's really easy to implement in a string driven state machine.
Mark Smith ([EMAIL PROTECTED]) www.highergroundbluegrass.com ____________________________________________________________________ Subject: RE: State machine diagram editor From: "Scott Serlin" <[EMAIL PROTECTED]> Date: Fri, 16 Jan 2004 11:17:53 -0600 Thanks for the info. I was hoping for a faster way to add and modify states to the state machine. Also, does anyone have any state machine tips that they can share? I typically use a string driven state machine. I then call out each state from other states. I also use a "nextstate" local variable so that I can reuse particular states in the machine over and over again and not have to replicate the state throughout the machine. Let me and the email list know your tips. Thanks. Scott
