[
https://issues.apache.org/jira/browse/FLEX-33205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curtis Aube updated FLEX-33205:
-------------------------------
Description:
This generates a stack trace:
var hgroup:HGroup = new HGroup;
var hbox:HBox = new HBox;
var label:Label = new Label;
hgroup.addElement(label);
hbox.addChild(label);
Expected behavior:
It should not generate a stack trace.
Workaround:
Call removeElement on the spark container before calling addChild on the mx
container.
Found by Norman Reed
was:
This generates a stack trace:
var hgroup:HGroup = new HGroup;
var hbox:HBox = new HBox;
var label:Label = new Label;
hgroup.addElement(label);
hbox.addChild(label);
Expected behavior:
It should not generate a stack trace.
Workaround:
Call removeElement on the spark container before calling addChild on the mx
container.
> Stack trace when moving a child from spark container to mx container
> --------------------------------------------------------------------
>
> Key: FLEX-33205
> URL: https://issues.apache.org/jira/browse/FLEX-33205
> Project: Apache Flex
> Issue Type: Bug
> Reporter: Curtis Aube
> Priority: Minor
>
> This generates a stack trace:
> var hgroup:HGroup = new HGroup;
> var hbox:HBox = new HBox;
> var label:Label = new Label;
> hgroup.addElement(label);
> hbox.addChild(label);
> Expected behavior:
> It should not generate a stack trace.
> Workaround:
> Call removeElement on the spark container before calling addChild on the mx
> container.
> Found by Norman Reed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
