|
|
policy troubles solved (code generation bug?) [message #210568 is a reply to message #210560] |
Thu, 06 November 2008 11:40 |
paolo russian Messages: 81 Registered: July 2009 |
Member |
|
|
paolo ha scritto:
> paolo ha scritto:
>> Hi, I've discovered that I've got an item A in my palette that is
>> meant to be child B.
>> Surprisingly, you cannot create A in B from the palette, but you can
>> do it if hovering over B and waiting for the baloon. The amazing thing
>> is that in the baloon there's the choice of adding A, and works.
>>
>> What's the issue, I mean what are the classes involved?
>> I need to reset it so that I can create normally A als o from its
>> palette tool!
>>
>> Thanks a lot.
>>
>> Paolo Russian
>
> Let me say the mapping is okay on my opinion.
well... er.. maybe this is a bug or something.
this is the generated method that brings up the powers to that widget
palette tool:
/**
* @generated
*/
private ToolEntry createTextBox13CreationTool() {
List/*<IElementType>*/types = new ArrayList/*<IElementType>*/(4);
types.add(ComponentsElementTypes.TextBox_2003);
types.add(ComponentsElementTypes.TextBox_3003);
types.add(ComponentsElementTypes.TextBox_3045);
types.add(ComponentsElementTypes.TextBox_3055);
NodeToolEntry entry = new NodeToolEntry(
Messages.TextBox13CreationTool_title,
Messages.TextBox13CreationTool_desc, types);
entry.setSmallIcon(ComponentsElementTypes
.getImageDescriptor(ComponentsElementTypes.TextBox_2003));
entry.setLargeIcon(entry.getSmallIcon());
return entry;
}
To resolve the issue, I added a
types.add(ComponentsElementTypes.TextBox_3019);
and placed the generated not, but this imho isn't that nice because if
in the future we are to modify the model nearby this tool perhaps we
won't realize there's a "generated not" it at a glance.
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03417 seconds