> DataProvider is not secretly decorating things, BUT something somewhere > in the V2 stuff is iterating over the array object itself, and is > silently blowing up when it finds these extra functions. I've had a > similar problem when some third party code was adding a function to > object.prototype, and the WebService object took a dump (it iterates > over a hash object and sees something weird and throws an error).
This is an example of poor coding by MM's component writers. You shouldn't be iterating through enumerable arrays using for (var a in this) because you're going to pick up all the methods of the Array object, as well. It's just sloppy coding due to how loose Flash is with its typing. I always try to write as careful code as possible to avoid the oh so enticing opportunities flash provides for sloppy coding. Things like if (!this.length) versus if (this.length == 0)... However, using ASSetPropFlags is the best solution to hide functions so they don't appear when you iterate through an Array object. _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
