Hi Chris,
> With the static array problem, it looks like you've found a bug.
Yes, I copied my example out of an email I sent to the product team about
it.
> With your listener problem, shouldn't the statement be:-
>
> var mclListener = this;
>
> I'm assuming that the function MapLayerModel is a method of a class mlm,
> so 'this' is referring to the current instance.
The line
var mclListener = {mlm:this};
Creates a new object with the {} operators, and then sets a property called
mlm to point back to this instance of MapLayerModel (who's constructor
function MapLayerModel() we're currently executing). The next two functions
are then added to this object - problem is that the functions can't refer to
the mlm property without Flash throwing a syntax error.
Actually while I was researching my memory usage problems I found an
interesting article about why creating classes on the fly like this wastes
memory - see:
http://timotheegroleau.com/Flash/articles/scope_chain.htm
Robin
PS: We tried the app on John's Mac laptop, it runs but rather slowly...
PPS: This isn't a showstopper for future performance improvements, I think
that moving some of the model stuff into shared objects and CF will have a
big effect on speed and memory usage.
"Chris Velevitch" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
---
You are currently subscribed to fugli as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/