-
This helps to understand which statechart is actually referenced in case there are multiple equally named statecharts in the project.
tkutz updated
5 years ago
-
I am trying to visualise a fairly sizable statechart (maybe 50 states, with 7 levels deep nesting), but get an error when going beyond level 5.
### Expected Behavior
Expect the SVG to be produce…
-
## Bug or feature request?
bug using version 4.0.0-4.0.1.
It worked previously on 4.0.0-13 and 4.0.0-15.
## Description:
using `assign` makes `action` "invisible".
## (Bug) Expected resul…
-
Hi Tomas,
Sorry to bug you again, I have another question about your library. I've studied the gmail example (to the extent of my abilities...). It seems like this library is meant to have a single…
-
In Solidity the operator precedence is different from the expression language used in YAKINDU Statechart Tools. Here, the precedence is the same as in Java and C.
This allows constructs in Solidit…
-
## Bug or feature request?
Feature request
## Description:
A way of extending `actionTypes` in the interpreter is needed. Is very common to use custom actions in statecharts, I want to take advanta…
-
Right-click in spec sec on element, choose refactor->rename, dialog opens, but the chosen new name is not accepted. The statechart does not change at all.
-
## Bug or feature request?
Feature request, unless it can already be done
## Description:
I would like to populate history after the machine has been initialised. The user will pass through some …
-
Related to #36 cc. @mogsie
Provide a separate _interpreter_ which will act as a simple event emitter for which to run a machine. This is technically side-effectful, but it is not a core part of how…
-
'Step Over' function for terminated simulations has no effect.
Time will not be proceeded, events will not be handled.