In the project semantic-order-msg-move.zip, I can move (without Ctrl pressed) the message AsyncMessage2 upwards beyond the lower end of AsyncMessage1, which is fine. However, the resulting graphical position is inconsistent with the (unchanged) semantic order, as detailed below.
This is the initial scenario:
Moving AsyncMessage2 upwards beyong AsyncMessage1 will lead to the following:
As can be seen above, AsyncMessage1 is nudged upwards, which is fine, however, it is not nudged enough, so that the send event of AsyncMessage2 (named 2s) is above the receive event of AsyncMessage1 (named 1r).
Note that just re-orienting message end 2s above 1r works fine.
In the project semantic-order-msg-move.zip, I can move (without Ctrl pressed) the message
AsyncMessage2upwards beyond the lower end ofAsyncMessage1, which is fine. However, the resulting graphical position is inconsistent with the (unchanged) semantic order, as detailed below.This is the initial scenario:
Moving
AsyncMessage2upwards beyongAsyncMessage1will lead to the following:As can be seen above,
AsyncMessage1is nudged upwards, which is fine, however, it is not nudged enough, so that the send event ofAsyncMessage2(named2s) is above the receive event ofAsyncMessage1(named1r).Note that just re-orienting message end
2sabove1rworks fine.