[quoted text, click to view] > The really anoying things is that if it was a text field that I
> wanted to detect a change in, it would be as simple as:
>
> my_txt.onChanged = function(){
> trace("Text changed");
> }
>
> and that it.
This is a convenient mechanism, for sure.
[quoted text, click to view] > But trying to apply this same functioning to a movie, well as
> you can imagine, is a little trickier.
Certainly, but a but movie (the FLA itself) is vastly different from a
TextField instance. As Gary suggested, this is probably a matter of looking
for different ways to architect your main timeline. If your main timeline
is being *sent* from one frame to another, you might consider adding
instructions to the function(s) doing the sending to also trigger your other
functions (the ones that would have been triggered by a "watch" on the frame
number).
Another suggestion was this ...
[quoted text, click to view] >> Can't you put an ActionScript in that frame to notify your Flash
>> movie, ie change a variable's value or call a function?
.... to which you replied ...
[quoted text, click to view] > That was an initial idea but the idea is to be able to load random
> .swf files into a main shell
.... but I don't see where that would be problem. You could load random
files into the main shell by using setInterval(), for example, or the above
mentioned trigger script in these frames. It all depends on how you write
your "receiving" functions, y'know? It sounds like you have a certain goal
and are comfortable with one particular way of dealing with it, except that
one way is hard on the processor -- so what are your other options? It's
hard for us to know without more details.
David
stiller (at) quip (dot) net
"Luck is the residue of good design."