Deleting message with nested behaviour in combined fragment broken

[Matthias Schoettle]

When removing the do() message in the screenshot below, the foo() message is not removed. However, the same works if not contained within a combined fragment.

Update: Just to explicitly point this out. The issue only occurs if do() has no return message as shown above.

[Matthias Schoettle]

With the proposed change in #425 to always have reply messages this would not be a problem. However, independent of this, there should be a test case that can catch this.

[Matthias Schoettle]

The is that the current implementation to find the last fragment index to delete, is based on finding the next fragment on the lifeline the message is originating from. Since there is no other fragment within the operand on that lifeline, the toIndex is fromIndex + 1.

So, unless a special case is used to determine this, the change proposed in #425 would simplify and solve it.

[Matthias Schoettle]

References #305: Adds test case to observe this issue.

→ <<cset 5a988d90aa4f>>

[Matthias Schoettle]

Resolves #305: Adds special case to ensure that toIndex is incremented.

The toIndex is incremented when the container is not the interaction, and for each fragment after the message being deleted. This ensures that even if there are no fragments on the same lifeline following the send event the correct toIndex is determined.

→ <<cset ee132b3c69d0>>