Bugzilla – Full Text Bug Listing
| Summary: | [Sequence Diagram] Improve Combined Fragment functionality | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Gabriel Merin Cubero <gmerin> |
| Component: | Core | Assignee: | Thibault Landré <thibault.landre> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | raynerv, sebastien.gerard, yaang.liu |
| Version: | 0.7.0 | Keywords: | plan |
| Target Milestone: | M2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | UML 2.x Diagrams | ||
|
Description
Gabriel Merin Cubero
CombinedFragment is improved. It managed the different InteractionOperator. It is also possible to create a ConsideredIgnoreFragment Depending on the InteractionOperator, the user is grant the right to add one or more Interaction Operand. If the user try to add more than one InteractionOperand on a CombinedFragment that only accept one InteractionOperand (for exemple loop), then a popup shows up to explain why he can't create this new InteractionOperand. If the combinedFragment contains more than one InteractionOperand, the user is not allowed anymore to change the InteractionOperator. Validation has revealed new bugs or problems : - 1/ The background color is initialized to black with default preferences, which is very confusing. - 2/ When a Combined Fragment is added in an Interaction Operand of a CF, the new CF can not be distinguished from the Interaction Operand (and label is not common to the two CF). Hence, when trying to add new Interaction Operands to the new CF, they are added to the oldest one. - 3/ When an Interaction Operand in a CF is deleted from the Model Explorer view, the figure is not removed. - 4/ When trying to set Interaction Operator to Consider or Ignore, a wrong reason is invoked for failure : The message tells it is because there is "more than one Interaction Operand" instead of explaining the value is reserved for a ConsiderIgnoreFragment. - 5/ When trying to set Interaction Operator when there is more than one Interaction Operand, the wrong reason is invoked. Message is switched with the case in 4/. - 6/ No min value nor guard is created on a loop Combined Fragment - 7/ When a lifeline is added to the property "covered", the figure is not enlarged. We must resize the figure to correct it. - 8/ CF can overlap each over - 9/ CF can not be drag n dropped. - 10/ When deleting a CF from Model Explorer, no popup ask whether executions and messages must be delete. Executions are deleted , Messages are not. - 11/ Delete from model does not work on CF Same bugs exist on ConsiderIgnoreFragment. *** Bug 298773 has been marked as a duplicate of this bug. *** - 1/ solved. -2/ solved -3/ Solved, it was missing the correct policy (removeOrphanView). - 4 / - 5/ Solved -11/ Delete from model has been improved. It works now, and several improvement have also been made on interaction operand "delete from model" action (In reply to comment #2) > Validation has revealed new bugs or problems : > > - 1/ The background color is initialized to black with default preferences, > which is very confusing. > - 2/ When a Combined Fragment is added in an Interaction Operand of a CF, the > new CF can not be distinguished from the Interaction Operand (and label is not > common to the two CF). Hence, when trying to add new Interaction Operands to > the new CF, they are added to the oldest one. > - 3/ When an Interaction Operand in a CF is deleted from the Model Explorer > view, the figure is not removed. > - 4/ When trying to set Interaction Operator to Consider or Ignore, a wrong > reason is invoked for failure : > The message tells it is because there is "more than one Interaction Operand" > instead of explaining the value is reserved for a ConsiderIgnoreFragment. > - 5/ When trying to set Interaction Operator when there is more than one > Interaction Operand, the wrong reason is invoked. Message is switched with the > case in 4/. > - 6/ No min value nor guard is created on a loop Combined Fragment > - 7/ When a lifeline is added to the property "covered", the figure is not > enlarged. We must resize the figure to correct it. > - 8/ CF can overlap each over > - 9/ CF can not be drag n dropped. > - 10/ When deleting a CF from Model Explorer, no popup ask whether executions > and messages must be delete. Executions are deleted , Messages are not. > - 11/ Delete from model does not work on CF > > Same bugs exist on ConsiderIgnoreFragment. Will 9 be fixed in the future release? Any schedule? This issue still active in 0.8.0 Thank you. Closed as fixed in 0.10.0. |