[Tweener] Positive to negative problems

[Dave Lenz]

Ok then...

My tween code (two event-listeners on a movieclip) is:
private function mouseOver(e : MouseEvent = null ) : void {
	var a:Number = -100;
	var b:Number = 255;
	Tweener.addTween( this, {_color_ra:a, _color_rb:b, _color_ga:a,  
_color_gb:b, _color_ba:a, _color_bb:b, time:.2,  
transition:"easeInOutCubic"} );
}

private function mouseOut(e : MouseEvent = null ) : void {
	var a:Number = 100;
	var b:Number = 0;
	Tweener.addTween( this, {_color_ra:a, _color_rb:b, _color_ga:a,  
_color_gb:b, _color_ba:a, _color_bb:b, time:.5,  
transition:"easeInOutCubic"} );
}

I'm using the '_color_xx' method now and I still get the same 'green'  
or 'magenta' but it's more sporadic than using the '_color'. Maybe  
it's because the rollover uses a time of .2 and the rollout .5.
I'm still going to try the 'removeTweens( this );' later on and I will  
let you know if that solved it for me.

And just for your information... we have a huge team of developers all  
loving (and hating sometimes) Tweener. We love the syntax and we love  
the diversity with all the 'shortcuts' etc.

Thanks in advance,

Dave.

Op 3 okt 2008, om 15:44 heeft Zeh Fernando het volgende geschreven:

> Hi Dave,
>
> The problem supposedly solved by the latest patch is some sort of  
> very strange bug that made something like that - creating cyan  
> colors - when you started Tweens too fast (for example, on  
> successive rollover and rollout of a button). The reason why this  
> bug is strange is because it's not really apparent why it showed up,  
> and it was dependent on some random compilation information - you'd  
> compile an SWF and always have the bug happen, then you'd compile it  
> again and never have it show up.
>
> Not sure if that's what you're having, but just to be more clear on  
> the fix.
>
> There's one other change by Francis Turmel I still have to commit  
> which is the ability to properly remove tweens by using their  
> "special property splitter" names, so a removeTweens for "_color"  
> can properly be done. This would probably help a bit on your case  
> since you'd be able to stop any tween before starting new ones and  
> "starting fresh". In the mean time, on your specific case, you can  
> try this:
>
> 1. Before starting a tween, do a removeTweens(objectname) to remove  
> all existing tweens (useful if you don't have other tweens on the  
> object); or,
>
> 2. Do a tween with the actual color properties  
> (_color_redMultiplier, _color_redOffset, etc)... this is of course a  
> bit more annoying to work with, but it gives you a lot more control  
> than just _color.
>
> Zeh
> _______________________________________________
> Tweener mailing list
> Tweener at lists.caurinauebi.com
> http://lists.caurinauebi.com/listinfo.cgi/tweener-caurinauebi.com
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.caurinauebi.com/pipermail/tweener-caurinauebi.com/attachments/20081004/d1b8947f/attachment.htm>