> You could consider letting the datagrid bear the burden of keeping > track of the selection like in this TileList example > http://blog.flexmonkeypatches.com/2007/09/10/flex-tilelist-with- > togglebuttons/
Good example, but I'm not convinced that a child should know, or control, a parent. The associative array is a cool solution. But creating a "myTileList" reference, inside the itemRenderer, limits the use of the itemRenderer for other controls, and seems a bit backwards (IMHO). Yes, the DataGrid (parent) could bear the burden; and should. All of the code in the itemRenderer, that accesses the parent, can be done in the parent itself; through the use of events. Subclassing DataGrid, or TileList, or whatever, in this case, might be a more pure approach; from an OO point of view. -TH --- In [email protected], "Amy" <amyblankens...@...> wrote: > > --- In [email protected], Simon Bailey simon@ wrote: > > > > Ok I am a numbnut! Rsolved through 2 seperate arrays, into two > > seperate arraycollections! > > > > I must add that if the 2 Array sources are different I then > result > > in the issue of multiple selections (CheckBox) on row and in > column. > > Are there any suggestions on how to overcome this? > > If the objects contained in each array are the same, then they will > have the same properties no matter where you're referring to them > from. > > You could consider letting the datagrid bear the burden of keeping > track of the selection like in this TileList example > http://blog.flexmonkeypatches.com/2007/09/10/flex-tilelist-with- > togglebuttons/ > > Hope this helps; > > Amy >
