Since I’m on a DataProvider trip this week, I am re-posting here what I posted today on <a href=”http://chattyfig.figleaf.com/cgi-bin/ezmlm-cgi?1:mss:61836:200302:bdcdaajbgklhcagkcngf”>Flashcoders</a>. I think it might have been lost in the OT Flame war going on over… well, war.
Anyway, if you want to know what the DataProvider actually broadcasts in it’s <code>modelChanged</code> event, here you go…!
I did some tests to see who “properly” handles the DataProvider’s <code>modelChanged</code> event. Not many, it seems. Now that I understand it, I don’t understand why they don’t utilize the power of this object, but anyway, here are my findings…
You know your a geek when <a href=”http://www.macromedia.com”>Macromedia</a> promotions enter into your family purchasing decisions.
For the past couple of months, a lot of my components blindly inherit from the FUIComponentClass in Flash. Blindly meaning I really didn’t know why I was other than it says in the comments that it is the base component of all Flash components, and all other components in the Macromedia sets do inherit from it in some way or another, so I figured I would follow suit. More important things to do than to investigate something as trivial as functionality I’ll probably not use for awhile, right? Well, <a href=”http://psychlonex.dyndns.org/”>John Robinson</a> and I this weekend walked through it, and we think we’ve figured out how it works… partly, as well as the DataProvider, and why the 1 frame update happens.