[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] gnash/testsuite/misc-ming.all

From: zou lunkai
Subject: Re: [Gnash-commit] gnash/testsuite/misc-ming.all
Date: Tue, 15 May 2007 09:39:05 +0800

I've seen what the bug is.
I think removeMovieClip is also affected, and who knows what else.

I'v thought about the "removeMovieClip ", it is also tested in this
testcase with a simple format. Note the way we call
"duplicateMovieClip" and "removeMovieClip" are different.
(1)  duplicateMovieClip("srcClip", "dstClip", depth);
(2)   removeMovieClip(target);

"srcClip" specified in "duplicateMovieClip" is a string. After
compile, it is still a string.
"target" specified in "removeMovieClip" is *not* a string, just a
reference of the target movieClip. We might not need to call
"find_target" in the implementation(I'm not sure).

To test if "removeMovieClip" is also affected, I guess I need to use
the "asm" block.

Could you add a test checking effect of being in a 'with' block
while calling duplicateMovieClip ?

As I wrote in the "expected behaviour":
"the source movie clip should be within the same timeline as the new
movie clip."

As "with" block will change the scopeChain, then if the "expected
behaviour" is correct, we can not duplicate a movieClip in another

Not so sure what to do now. I guess we should confirm if the
"expected behaviour" is correct first.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]