Add support to create reply messages
Issue #236
resolved
Currently it is not possible to create additional reply messages in message views.
This can potentially be done through the menu when tap-and-holding on a spacer (of the first lifeline and if the initial message returns something other than void).
Comments (8)
-
-
reporter
The same would be good for self messages, since it is not visible to the user how a self message can be done and difficult to actually trigger the creation.
-
reporter
Hm. I think we need to constrain the locations of where it is possible to create reply messages since it makes no sense to just create a second reply in a normal flow with no combined fragments.
I.e., it should only be allowed to create them inside a combined fragment and at the end of an operand.
-
reporter
References issue
#236: Added the ability to create a self message from the menu when performing tap-and-hold on a lifeline.→ <<cset e892881d7e4b>>
-
reporter
References issue
#236: Added ability to create reply messages. They can be only created inside combined fragments and at the end of the enclosing operand.Right now reply messages can only be created for the operation the message view defines, because additional reply messages in "nested behaviour" are a bit tricky. The lifeline where the reply goes to would need to become part of the combined fragment and there are additional problems left to be resolved. For now, in such a case its own message view should be defined.
→ <<cset 04f39f620bf9>>
-
reporter
- changed status to resolved
Resolved with merge of pull request #8 into master.
-
reporter
References
#236: Adds the removal of a Gate when a reply message is deleted.→ <<cset 00ad5b2cc2ec>>
-
reporter
References
#236: Fixes determining whether a reply message is allowed at a certain index. In case of a message with potentially nested behaviour as the last element in an operand, the previous way did not work properly.→ <<cset 59af02c1b3b2>>
- Log in to comment
Good idea!