I’ve been fighting implementing FUI Component inheritance into some of my existing components at work. I’ve been battling with it for 2 days, and I can’t wait to publish the results of my work: How to play nice with FUI. Stay tuned.
When stressed out of my gourd (like now), I love to escape to the <a href=”http://icewind2.blackisle.com/” target=”_blank”>Icy North</a>. Where do you go?
<a href=”https://www.jessewarden.com/archives/Dragon’s Reach.jpg” target=”_blank”><img src=”https://www.jessewarden.com/archives/Dragon’s Reach thumb.jpg” border=”0″ /></a>
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…