1) Yes, this works fine, for the display portion only. It doesn't address the actual problem of needing to set a flag in the data that indicates it is the currently highlighted one, that flag being also used by other things that bind to the data that don't want to know about UI details like the grid. In this case, I had a number of chart listeners that would toggle series on/off depending on which one was highlighted in the grid.
2) There is no commitProperties on AdvancedDataGridItemRenderer. Perhaps you meant validateProperties. In this example, it gets called only when the grid is first displayed and not when any item is highlighted/de-highlighted or selected/de-selected. 3) Yes, the styleFunction does get called when the highlighted object changes. But if you move the code to set data.highlighted there, you get the same result! It just seems like anything that changes this bound variable on every repaint of the cell is doomed to break the rollover highlight. On Tue, Jun 9, 2009 at 11:49 AM, Amy <[email protected]> wrote: > > > --- In [email protected] <flexcoders%40yahoogroups.com>, Pan > Troglodytes <chimpathe...@...> wrote: > > > > That was a good idea and it does get rid of the arraycollection walking. > > But I get the SAME problem with the grid losing highlighting when I did > it > > using AdvancedGridItemRenderer, thought the symptoms are slightly > different: > > Personally, I'd do one of two things: > > 1) Just look to see if the current item is the highlighted item in the > styleFunction > > -or- > > 2) Override commitProperties instead of validateNow(). > > I'd also be tempted to investigate whether the styleFunction gets called > when the highlighted object changes. > > HTH; > > Amy > > > -- Jason
