Skinning the Flash DataGrid (Part 2)

25 Feb

I keep fighting to make my DataGrid look just like my Ad agency desires and todays biggest problem was a bug in the DataGrid component that renders the “backgroundColor” style for it useless. No matter what color I set, it turns up as the same shade of red… How to get around that then? I could start digging around the class files again, but it didn’t feel too tempting. What other solutions are there then?

After some searching around, what looked the best was the $5 DataGrid extensions by Tufat (and Darren Gates?). At $5, it’s almost too cheap? Anyway - it’s a great extension that offers sorting numerically (how could MM omit that?), HTML display, editing, text wrapping, turning off the gridlines and much more. It even gives you proper coloring of rows that allow you to combine alternating rowcolors and custom column colors. The $5 gives you not only a SWC, but the full Source Code as classes so you can modify them as you like. Very neat!

Only problem is that when I extend it, my checkbox cellrenderer fails to render properly. Oh well. Working on it… smile

25 February 2006 at 2:39 am

2 Responses to Skinning the Flash DataGrid (Part 2)

  1. avatar photo
    Mircea 08 April 2006 at 8:51 am #

    Hi!

    I have exactly the same problem with the TuFat datagrid extension…

    Have you found any solution for this?

    Thanks,
    Mircea

  2. avatar photo
    Jensa 08 April 2006 at 6:05 pm #

    Hi Mircea,
    Yup. I found a solution, but it’s not ideal so I haven’t posted it yet. It’s really easy to get around this. The component version will work fine, but the class-based version fails. The solution is to NOT include the Tufat classes by adding them to your project or referencing them. This will cause the complier to complain and throw a couple warnings but the cellRenderers will work as intended.

    I researched the problem for quite some time but finally figured that it was not my job locate all the bugs. I’ve emailed Darren Gates (the guy behind the Tufat extensions) my changes and he never bothered replying. He also does not reply in his own support forum either. If he can’t be bothered to reply, I won’t be bothered to fix his code to silent the compiler. So - great classes, but crappy support. I guess that’s what you get when buying a $5 extension rather than $29 or $59? If they worked flawlessly, I’d gladly pay that much for his extensions.

  3.