As a very general word of warning, I'd advise you to be more careful and expect more pain when working with the following classes (and all associated base classes, etc): AdvancedDataGrid, OLAPDataGrid, GroupingCollection.
I'll try to be extremely politically correct here, but I assume you'll catch my drift... These classes were written by a different part of the Flex team, in a different part of the world, and they are quite different than the standard Flex framework code base. They often don't follow the same coding standards, and in my opinion they are not up to the same quality level that I have come to expect from the Flex framework. I'll stop at that before I make too many Adobeans mad at me, but just know that I've learned to expect a whole new kind of pain when working with those classes. Doug On Thu, Jun 26, 2008 at 3:04 PM, Amy <[EMAIL PROTECTED]> wrote: > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, "Amy" > <[EMAIL PROTECTED]> wrote: > > > > --- In flexcoders@yahoogroups.com <flexcoders%40yahoogroups.com>, > "Jonathan Branam" > > <jonathan.lists@> wrote: > > > > > > There are a bunch of comments below, but to sum up, it seems like > > extending > > > AdvancedDataGridGroupItemRenderer and drawing a background with > the > > graphics > > > property will meet all of your needs. I missed the requirement to > > preserve > > > leaf icons and such. Is there a reason this doesn't meet your > > needs, because > > > you seem to have known this already? > > > > I didn't know that I could use my patched > > AdvancedDataGridGroupItemRenderer as the regular itemRenderer as > well > > and have it just work. I assumed that there are two distinctly and > > yes irritatingly different classes for a reason. > > > > It turns out I am having a problem dynamically setting the icon on > > leaf nodes... when I use an iconFunction, the function returns the > > right thing but it is never drawn (even with changing out the > > itemRenderer). When I use a groupIconFunction, it only runs for > the > > items that are parents. > > That, at least, was solved relatively painlessly. Before I realized > there were two different classes handling the rendering, I forced the > first column to my patched regular ADGItemRenderer (because that put > the color in more rows in that column). So the only time it used my > GroupItemRenderer was when it actually was displaying a group, which > seems to override the hardcoded itemRenderer. > > >
