Default History States

[GoogleCodeExporter]

This is a query rather than a bug:

What steps will reproduce the problem?
1. Create a history node in a cluster node
2. Create other sibling nodes
3. Connect transitions from the history node to multiple child nodes

What is the expected output? What do you see instead?
Should I expect to see a warning that a history node has multiple target nodes 
where the nodes are not part of a parallel state?
I understand that it is possible to have multiple default states from a history 
node and that these are indicated by the transitions.
Under what circumstances would transitions from a history node be illegal and 
should the editor be reporting them as invalid?

From http://www.w3.org/TR/scxml/#history

We also define the states specified by the 'target' of the <history> element's 
<transition> child to be the 'default stored state configuration' for that 
element.

What version of the product are you using? On what operating system?
Version 179, Windows 7 32 bit

Original issue reported on code.google.com by miketrah...@gmail.com on 29 Jan 2013 at 7:51

[GoogleCodeExporter]

sorry but i don't know. Try asking your question in a scxml mailing list, for 
example that of the Apache scxml interpreter.

Original comment by fmorbini on 30 Jan 2013 at 5:21

[GoogleCodeExporter]

Original comment by fmorbini on 1 Feb 2013 at 4:49

• Changed state: Invalid