Sorry for the confusion, but after re-reading your email I realize that you are asking the question instead of saying that the state machine *will* be rethought.
On Fri, Feb 15, 2008 at 2:30 PM, Mark Webb <[EMAIL PROTECTED]> wrote: > hrm. Would this be an API change? If so, do we want it in the 2.0 release? > > > > On Fri, Feb 15, 2008 at 2:28 PM, Rodrigo Madera > <[EMAIL PROTECTED]> wrote: > > Don't want to be bad here, but are there any plans to actually rethink this > > state machine framework to make it friendlier? > > > > Rodrigo > > > > > > > > On Fri, Feb 15, 2008 at 7:24 PM, Mark Webb <[EMAIL PROTECTED]> wrote: > > > > > I have been trying to write a MINA system using the state machine > > > library. As I go through the documentation I think I found an error > > > that is confusing me. So either I am just simply confused or there is > > > an error :) > > > > > > Looking at the diagram, I think the transition from "Paused" to > > > "Playing" should be "play". This would allow the @Transitions > > > annotation in TapeDeckHandler to make more sense, since this > > > annotation appears to support multiple @Transition annotations for one > > > state. > > > > > > Thanks in advance for any clarification > > > Mark > > > > > > -- > > > -------------------------------- > > > Talent hits a target no one else can hit; Genius hits a target no one > > > else can see. > > > > > > > > > -- > > > -------------------------------- > Talent hits a target no one else can hit; Genius hits a target no one > else can see. > -- -------------------------------- Talent hits a target no one else can hit; Genius hits a target no one else can see.
