the ends 1s and 1r denote the send and receive event of the AsyncMessage1, respectively. If I now move (with Ctrl pushed) AsyncMessage1 lower than AsyncMessage2, the order of the ends is not updated correctly:
This is also partly reproducable when moving up AsyncMessage2. Only the send event is re-ordered correctly. But the receive event, isn't.
Note that all works fine for both cases, if we don't move the message, but re-orient the message ends one by one.
I imagine this is closely related to #427, which is a problem of the semantic order being fixed too early, after the send event of a message is updated but before the receive event.
In the project semantic-order-msg-move.zip the initial state is as follows:
the ends
1s
and1r
denote the send and receive event of theAsyncMessage1
, respectively. If I now move (with Ctrl pushed)AsyncMessage1
lower thanAsyncMessage2
, the order of the ends is not updated correctly:This is also partly reproducable when moving up
AsyncMessage2
. Only the send event is re-ordered correctly. But the receive event, isn't.Note that all works fine for both cases, if we don't move the message, but re-orient the message ends one by one.