Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: PeterHeintz on September 27, 2016, 11:21:38 pm
-
When you have connected states with transitions and changed line style to Bezier and you add a new transition within the diagram all transitions switch back to Auto Routing.
This seems to happen for any line style changes from default (Auto Routing) to any other.
Observed in build 2015 and new V13 versions.
-
When you have connected states with transitions and changed line style to Bezier and you add a new transition within the diagram all transitions switch back to Auto Routing.
This seems to happen for any line style changes from default (Auto Routing) to any other.
Observed in build 2015 and new V13 versions.
I can't reproduce. It sounds like EA reverting to the previous saved version of the diagram. Does it still happen if you save the diagram before adding the new transition? But why would EA reload the saved diagram without warning of unsaved changes? Do you have any addins running?
-
Thank you KP,
Pointing me to addins helped me to catch the devil. It is the hoTools addin who changes the line style.
Maybe Helmut can response on this post.
-
Hello,
thanks for remembering me. I've read it but not recognized that's my issue. Sorry!!
Yes, hoTools has the ability of defining a default line Style for a Diagram type. I think the default settings isn't that good.
In hoTools Settings you can define diagram type and default Line Style. Just disable it.
Kind regards,
Helmut
-
Ok Helmut!
In General Settings of hoTools I set „Linestyles and more“ to "Disable" and deselected „Linestyle Support“, but that was not successful (or what I thought what it should do).
What solved my problem was setting “Setting default Linestyle”/”Statechart” to “no”.
So, that is ok for me, however setting “Statechart” to something else is not “default” but “force”.
-
I have a similar problem in my default linestyles script when called from EA-Matic. It always removes the navigability information, even if you chose for a "from source to target" association. Still need to figure out what is going on there. I suspect a bug in the API.
Geert