Re[2]: [Gnash-dev] Weird actionscript bug

[Udo Giacomozzi]

Hello zou,

Friday, December 7, 2007, 3:25:24 AM, you wrote:
zl> hmm,  gotoFrame is even more important if it is buggy.

As said in IRC, with little modifications in the test case you can see
that too.

- change gotoAndStop to gotoAndPlay
- add a trace("baaad") in frame 4
- happens only when flushHigherPriorityActionQueues() patch applied
  (ActionExec.cpp:470 commented out)


Symptoms: Gnash just prints "baaad", does not execute the trace()s in
frame 3.

Code:
-------------8<----------------------------------------------------

// ### FRAME 1 ####################################################

function local_whatever() {
        return getTimer();
}

stop();

setInterval(
        function() {
                if (_currentframe!=1) return;
                
                gotoAndPlay(3);
        }

        ,1000);

        
// ### FRAME 3 ####################################################

stop();

function init_me(obj) {
        trace(obj+" --> 1 =");
        trace(obj+" --> 2 == / "+local_whatever());
        trace(obj+" --> 3 === / "+local_whatever());
        trace(obj+" --> 4 ====");
}

// ### FRAME 4 ####################################################

trace("baaaaad!");

// ### FRAME 1 OF MOVIECLIP #######################################

_parent.init_me(this);

-------------8<----------------------------------------------------


Compiled SWF attached.


Udo

init-order2.swf
Description: application/shockwave-flash