Eclipse Community Forums: Papyrus » Customized Palette for Stereotypes with String Properties

Help

Home

Home » Modeling » Papyrus » Customized Palette for Stereotypes with String Properties

Show: Today's Messages :: Show Polls :: Message Navigator

Customized Palette for Stereotypes with String Properties [message #962727]

Mon, 29 October 2012 09:26

Simon Schwichtenberg

Messages: 127
Registered: September 2011

Senior Member

Hi,

I have a profile that contains stereotypes with a string property (multiplicity 1) and extends CombinedFragment. As default value I set LiteralString with an empty string. I registered the profile using the extension point org.eclipse.papyrus.uml.extensionpoints.UMLProfile.

In the runtime workspace, I created a customized palette. I selected the tool for the CombinedFragment and set the list of applied stereotypes. When I use the tool, the stereotype for the drawn CombinedFragment is not applied.

It does not matter if the aggregation of the property is set to "none" or "composite".
It does not matter if I check the property in the "Stereotypes to Apply" section of the palette customization dialog. The only difference then, when I draw the stereotype, I get an additional dialog "You can edit there properties". But the stereotype is not applied anyway.

Is this a bug of Papyrus, am I using the palette customization wrong or is there something from with my profile?

Regards,
Simon

Report message to a moderator

Re: Customized Palette for Stereotypes with String Properties [message #1066741 is a reply to message #962727]

Thu, 04 July 2013 07:52

Dennis Stampfer

Messages: 23
Registered: April 2013

Junior Member

Report message to a moderator

Re: Customized Palette for Stereotypes with String Properties [message #1066791 is a reply to message #1066741]

Thu, 04 July 2013 11:34

Camille Letavernier

Messages: 952
Registered: February 2011

Senior Member

Hi,

I think some elements are not compatible with the Custom Palette framework. If the same steps work for other elements, then you should open a new bugzilla entry.

Regards,
Camille

Camille Letavernier

Report message to a moderator