Community
Participate
Working Groups
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.
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.
(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
- 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)
Fixed