Hi Christian,
So I foresee some conflicts if you have also worked on canonical synchronization and children strategies ;-) To help the work on transitions, I had to adapt a bit and to enhance the way canonical mode works for UML-RT state machines.
I had the issue of transitions displayed into a diagram where they should not. I planned initially to fix them by modifying the view providers. That would be the best solution, but there is no solution AFAIK to totally remove a provider from the view service and I am "polluted" by the Papyrus generic one. So I took the issue on another point of view, and I came modifying the canonical edit policy, or more precisely, the RT state machine children strategy. That's good that we discussed that topic, as I may also introduce a solution not viable when the inheritance will be in place. I check that the transition is contained in the "only" region displayed at screen. I ensure I do not have too much when running canonical policy. But there may be some troubles in cases of inheritance...
I will let you commit and do the merge on top of your contribution. I had 2 failing tests on the remote server [1] , where successful on the local machine. So I can wait before merging.
Cheers,
Rémi