| order of generated setters [message #128864] |
Tue, 18 July 2006 12:38  |
 hung
Messages: 117
Registered: July 2009 |
Senior Member |
|
|
Hello,
My ContainmentHandler looks something like this,
public Object contributeToDropRequest(...)
{
if ( .... )
{
preCmds.append(new AddComponentRenderingCommand(....));
}
......
}
My AddComponentRenderingCommand looks something like this :
public class AddComponentRenderingCommand extends CommandWrapper
{
public void execute()
{
setStructuralFeature("property1","\"value1\"");
setStructuralFeature("property2","\"value2\"");
setStructuralFeature("property3","\"value3\"");
}
}
I notice that when dragging my custom composite from Palette, the property
setters are generated in different order, For example:
I expect to see :
setProperty1("value1");
setProperty2("value2");
setProperty3("value3");
However, sometime I see this :
setProperty2("value2");
setProperty3("value3");
setProperty1("value1");
And when VE preview this composite, the setters are executed in some other
orders too.
Can someone tell me what exactly determines the order of the generated
code, and the execution when previewing? Thanks.
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03032 seconds
] 
Search
Help
Register
Login
Home
