[Top][All Lists]

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

Re[2]: [Gnash-dev] Re: gotoAndPlay bug in Gnash

From: Eric Hughes
Subject: Re[2]: [Gnash-dev] Re: gotoAndPlay bug in Gnash
Date: Wed, 09 May 2007 11:05:22 -0600

At 10:41 AM 5/9/2007, Udo Giacomozzi wrote:
Wednesday, May 9, 2007, 6:16:13 PM, you wrote:
EH> I also see the utility of being able to rewind simple scripts, for some
EH> certainly-yet-to-be-determined definition of "simple".

Rewinding a movie, using gotoAndPlay is nothing special. In fact, I
bet gotoAndPlay() is the most used ActionScript-function!

Rewinding to a previous execution state and going to a particular point of execution are distinct and very different operations. gotoAndPlay is of the latter type. It is not rewinding to some previous state, merely moving a current execution point.

In a different posting:
At 09:55 AM 5/9/2007, Udo Giacomozzi wrote:
Rewind a movie means (much simplified): restore the state of all
originally *static* instances in that frame.

Wait a minute. Is anything really restored, by which I mean, reverted to a previous state? Or are these instances simply added to the frame as if GOTO were absent and the frame were duplicated as the next frame?

There seems to be an inconsistent story here about what's happening. When a GOTO executes, does it restore something (which I would consider "something special") or doesn't it ("nothing special")? I can see that it might have to display something; fine. Does this display act like a restoration or like an initial display?

I can understand a desire to avoid recomputation, but _that's_ a caching or memo issue rather than a behavior-definition one.


reply via email to

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