Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 350682

Summary: [Sequence Diagram] Improve the Property Views for different kind of Messages
Product: [Modeling] Papyrus Reporter: Camille Letavernier <cletavernier>
Component: CoreAssignee: Camille Letavernier <cletavernier>
Status: CLOSED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: Chokri.Mraidha
Version: 0.8.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 358077    

Description Camille Letavernier CLA 2011-06-29 06:57:19 EDT
Papyrus shall provide different property views for the different kind of messages.

The following sorts need a specific view :

- SynchCall
- AsynchCall/AsynchSignal
- Reply

A message's signature (which is a derived property) should also be editable.

Moreover, when assigning a Signal to an AsynchCall message signature, or an Operation to an AsynchSignal message, a refactoring of the MessageEvents should be done.
Comment 1 Camille Letavernier CLA 2011-06-29 09:22:49 EDT
Partially done in r4917 :

- The signature is editable from the property view
- The refactoring for AsynchCall and AsynchSignal is done correctly
- The property views are split

The different kinds of property views still need some refinements.
Comment 2 Camille Letavernier CLA 2011-06-29 10:37:59 EDT
(In reply to comment #1)
> Partially done in r4917 :
> 
> - The signature is editable from the property view
> - The refactoring for AsynchCall and AsynchSignal is done correctly
> - The property views are split
> 
> The different kinds of property views still need some refinements.

Changes merged to the trunk on r4919
Comment 3 Camille Letavernier CLA 2011-07-12 10:07:24 EDT
- The Message property view has been improved :

The argument creation now depends on the parameters of the message's signature, when it is an Operation. Valid instances are filtered, and the argument's name and type are pre-filled with the parameter's ones.

- The InstanceValue's "instance" feature is now filtered to show only the valid instances
	- For an Enumeration, only the enumeration's literal are displayed
	- For other Classifiers, only the valid InstanceSpecification are displayed
	
Changes have been committed with r5024 (0.8.1 branch) and r5025 (0.9 trunk)
Comment 4 Camille Letavernier CLA 2013-08-06 09:24:29 EDT
Fixed