Yeah, we really need to clean up this whole concept of early/middle/ late setters, immediate/once/when/path/style constraints. They are a big ball of mud and just too unpredictable.

I think what we really want is for the constructor for each class to handle the various initial properties of the class and just write it out by hand in order. I'm looking at a bug Maynard filed where if you give a view a multi-frame resource you don't want to play, you can set play to false, but if the resource is set by a style constraint, you have to _constrain_ play to false. This is all because the of the magic order in which attributes get processed.

I just don't know where we are going to get the cycles to straighten this all out though.

On 2008-01-12, at 22:33 EST, Henry Minsky wrote:

While debugging the swf9 LzText class, I notice that __setFormat seems to be
getting called about four times when
an LzText is created. This seems very inefficient, I need to check if this
is happening in swf8/dhtml runtimes. The multiple
calls are all due to various setters firing for setFont , setFontSize,
setText, etc.

If these really are getting called multiple times, and this isn't just a bug
in my swf9 implementation, then we
ought to be able to consolidate all of these into a single call at the end
of exeuction of the constructor, which should speed up text creation.



--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

Reply via email to