It just clicked. One of those realization moments...
I'm guessing any instance of a child can only have one parent. Therefore this
someContainer.addChild(imageVar);
someOtherContainer.addChild(imageVar);
Is not OK, because references to imageVar don't get cleaned up as Flex
draws the screen. If
Forgot to mention it doesn't really matter about the image name - it
doesn't have to exist. I just had it as a test image in my project
directory...
-Ciarán
On 11/6/06, Ciarán [EMAIL PROTECTED] wrote:
I fixed the problem by changing the way I was using the Image control
(calling load() instead
I fixed the problem by changing the way I was using the Image control
(calling load() instead of changing the reference in the container).
callLater() would solve the issue if it were caused by event timings,
and I tried using that, so I don't think my problem is related. After
much tinkering
Ciaarán where do you add your child? what container?This error that happens seems that out of bounds it's because you're trying to attach a new child in the not supported container.Regards
On 11/2/06, Ciarán [EMAIL PROTECTED] wrote:
Hi All,
I'm having a
I'm having the exact same type of problem swapping containers in a
TabNavigator using this type of command
main.setChildIndex(main.getChildAt(2),1);
The behind code seems to choke on the getChildAt of the container.
I had the some index problems on other things with this component and for
that
5 matches
Mail list logo
