Can't you just change testerFx.set to testerFx.start ?
if you look at the framework source you can see set is not given an event:
set: function(now){
return now;
},
You could possibly change this to:
set: function(now){
this.fireEvent('complete', this.subject);
if (!this.callChain())
this.fireEvent('chainComplete', this.subject);
return now;
},
I haven't tested this or anything, just thinking out loud.
From: [email protected]
[mailto:[email protected]] On Behalf Of Roman Land
Sent: Monday, March 01, 2010 3:35 PM
To: [email protected]
Subject: [Moo] Re: chainis not called after FX completes when using "set" -
bug or design?
I know Sunday.. but now its Monday, some love this way? :)
On Sun, Feb 28, 2010 at 3:11 PM, Roman Land <[email protected]> wrote:
Hi,
To show you what I mean, read the code and follow three steps in the
mooshell:
http://mootools.net/shell/UPevc/
I checked the code and I see that when Fx.Tween.set is used, the Fx.step is
never called (for obvious reasons) and the "complete" event is never fired,
thus the chained functions are never called..
In the code this is by design, but in reality I want to keep my code clean
and simple and I sometimes switch between .set and .start for the Tween
effect.
As you can see in the mooshell, there's a weird buggy side effect that
happens due to the .chain registering with the chained functions array but
never fired (as mentioned above)
Nothing in the documentation mentions no chain support for Fx.Tween.set, so
this is either a documentation erreta or unwanted behavior...
Happy coding!
Roman
--
---
"Make everything as simple as possible, but not simpler."
- Albert Einstein
--
---
"Make everything as simple as possible, but not simpler."
- Albert Einstein
