In mbeddr's state machines, the transitions live under a state (under the state they "leave"). As a consequence, the subsitute info thingy does not really work, because I don't have a way of specifying the collection in which the new element will live.
In the screenshot below, the "contents" slot is the collection of state machine contents. I am not sure if the table API can be changed to accomodate this structure,
or whether we have to change mbeddr's state machines.
You can now directly specify the concept. The idea of specifying the "child path" was to automatically instantiate the required "wrappers", but that is not implemented yet.
In mbeddr's state machines, the transitions live under a state (under the state they "leave"). As a consequence, the subsitute info thingy does not really work, because I don't have a way of specifying the collection in which the new element will live.
In the screenshot below, the "contents" slot is the collection of state machine contents. I am not sure if the table API can be changed to accomodate this structure, or whether we have to change mbeddr's state machines.
Let's talk.