The well formedness rule - "There have to be at least two composite substates in a concurrent composite state" - seems to be enforced by the application rather then by crtics.
As you probably know its my opinion that we should seek some balance to enforce or hint different rules where it really aids the user to get the design right first time. So here is one to discuss. It surprised my to find that the button to create a new Concurrent Region on a Composite State actually creates 2 if there are currently zero. There is also the nasty hack to delete the remaining one if we get down to just one (that probably won't work under all circumstances). So should I make my job easier by removing the enforcement of this rule or should I make this enforcement better by managing it in the model subsystem? The enforcement doesn't fully enforce as it currently allows zero composites, is that good or bad? Possibly it's a balance between enforcement and critics? Bob. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
