[Top][All Lists]

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

[Gnash-commit] gnash/testsuite/misc-swfc.all opcode_guard_test...

From: Zou Lunkai
Subject: [Gnash-commit] gnash/testsuite/misc-swfc.all opcode_guard_test...
Date: Thu, 08 Nov 2007 06:00:20 +0000

CVSROOT:        /sources/gnash
Module name:    gnash
Changes by:     Zou Lunkai <zoulunkai>  07/11/08 06:00:20

Modified files:

Log message:
        get rid of misleading comments, it was a bad deduction from a bogus 
tests. Now, all onButtionActions are immune to opcode guard, feel better:)


RCS file: /sources/gnash/gnash/testsuite/misc-swfc.all/,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
---       8 Nov 2007 05:29:44 -0000       1.1
+++       8 Nov 2007 06:00:20 -0000       1.2
@@ -131,7 +131,7 @@
         .show b3 as=pressed
-            _root.asExecuted5 = true;
+            _root.asExecuted4 = true;
     .put btn1 x=0 y=300
@@ -143,7 +143,7 @@
     .del btn1
 .frame 32
-        _root.check_equals(asExecuted4, false);
+        _root.check_equals(asExecuted4, true);
@@ -152,12 +152,6 @@
 //   remove the button at frame X+2!
 // observed insane behaviour:
 //   opcode in onButtonPress is NOT guarded by isUnloaded()/isDestroyed() in 
this case
-// comments:
-//   the behaviour is strange to me! As it is not consistent with test1~3, 
-//   all opcode guard works as expected. But this is a very common case is 
real swfs.
-//   And many of the confusing bugs were caused by the onButtionActions.
-//   Seems the difference is caused by the removing time of the buttons. 
-//   show similar cases. 
 .frame 33
     .button btn2
         .show b1 as=idle

reply via email to

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