Closed himi closed 3 weeks ago
After this fix, the example below:
package TestFlowConnection2 {
action a0 {
first start;
then
action a01 {
action a001 {
out o1;
}
succession flow from a001.o1 to a002.i1;
action a002 {
in i1;
}
}
}
}
is properly rendered as:
I noticed this limitation hard to find if it happens. I changed to show an error message when the visualizer hits the limitation. So, if `SHOWLIB' style is enabled, the example above is rendered as:
Since
start
action is a standard library element having lots of features, the visualizer needed to process them, exceeding the limit of elements that can be processed, even though theSHOWLIB
style is not selected. This PR fixes the issue by preventingVPath
from traversing standard library elements ifSHOWLIB
style is not specified.This PR also adds a style configuration to
SuccessionFlowConnectionUsage
to properly render it and an error message shown in cases when the visualizer still hits the element limit.