State Machine: Transition's Trigger can't be null

Jan 19, 2011 at 11:09 PM

Maybe I'm missing something but why can’t a trigger be null?  The example in the documentation shows a bunch of Delay activities which seems useless in a real application; so why have them at all?  I’d expect to trigger based on an event, message, or condition.  The State Machine Toolkit on Code Project uses messages which is nice an intuitive.  Based on the example in the documentation I’m tempted to add Delays with TimeSpan.Zero everywhere and then use the condition to determine whether the transition should take place, but that seems very odd.  I though Receive might be what I wanted but it's a WCF thing.

WF4 State Machine Driven WPF UI seems like a better example to follow but it seems like the activities they created should be built into the activity pack.


Feb 25, 2011 at 8:21 PM

In the final State Machine release we support the concept of a Null transition (which is just like a delay with 0 time)