Nested ArrayCollection

Question

I have an ArrayCollection of 3 arrays: level0, level1, and
level2. The level0 array item a set of x,y coordinates. The level1
x,y coordinates are used to position ten objects relative to the
position of the level0 object. Similarly, the level2 x,y
coordinates are used to position ten objects relative to the
position of a level1 object.
I wish to designate the position of an object, say an HBox,
with code something like:
<mx:HBox
x="{Number(nodeCoordinates.level0[0].x)+Number(nodeCoordinates.level1[3].x)+Number(nodeCo ordinates.level2[9].x)}"
/>
When I compile the code I get the followign error message:
"1119: Access of possibly undefined property level0 through a
reference with static type mx.collections:ArrayCollection."
I know this isn't a clean way to address the problem. At this
early point I'm just trying to heavy-handedly get the app to do
want I want. I'll make the code more efficient later.
How can I reference and use the values in a nested
ArrayCollection?
Thank you in advance!

Answer 1

"[email protected]" <[email protected]>
wrote in message
news:gjp8g6$ahg$[email protected]..
> Thank you! Yes, your solution works as advertised,
including the compiler
> warning. :)
>
> I've been trying different means of using the getItemAt
method to
> eliminate
> the warnings, but have come up with the proper syntax
that recognizes
> nested
> arrays in an ArrayCollection. The getItemAt method
accepts an integer
> parameter. Does that mean I can't reference a nested
array?
>
> Layout of components needs to be pretty specific. So,
I'm not able to use
> the
> relative means for component layout.
You could try something like
x="((nodeCoordinates.getItemAt(0) as
ArrayCollection).getItemAt(0) as
YourDataType).x..."
But I think what rtAlton is trying to say is that there's an
implication
here that you've got a "thing" at level 0 that has an x
coordinate, and then
you have another "thing" placed at level1 relative to the
first thing, and
then there's this HBox that's being positioned relative to
the level1
object.
So it seems like you could do something that puts the level 0
and level 1
values into a variable and adds them together, then the level
2
ArrayCollection is pulled out as a separate variable,
simplifying the
references. Possibly this could be done with custom
components that
encapsulate each level.
HTH;
Amy