thecocce / actuate Goto Github PK

When I use a simple EaseOut animation to rotate and move an item:
Actuate.tween(item, 2, { rotationY:90, x:10, z:10 } ).onComplete(function() {});
its a bit stuttering at the end (subpixels?). It will stop for some frames and 
then move a pixel at the end. Is there some kind of rounding problem somewhere 
in the easing functions? Flash-Tweens [AS3 based] don't stutter and ease out a 
bit better

There seems to be a bug where objects are wronly clipped when they go to far to 
the left off the stage.

Here is a screenshot of the situation:
http://imageshack.us/g/510/s01t.png/

The circle with an 'i' in it is ok on both images. Another similar image at the 
lower left corner gets partially or completely clipped depending on the degree 
of rotation. The two screenshots show the problem at different times (it's 
animated).

I noticed that it does happen on cpp targets but not on flash.

What steps will reproduce the problem?
// haXe but same behavior with AS
package ;

import com.eclecticdesignstudio.motion.Actuate;
import flash.Lib;
class Main 
{   
    static function main() 
    {
        var m:Main = new Main();
    }
    public function new()
    {
        Actuate.update(test, 1, [1],[10]).onComplete(function() trace('onComplete'));
    }
    function test(a)
    {
        trace(a + ' updated');
    }

}
// traces
// ...
// onComplete
What is the expected output? 
onComplete should fire last but there is a last funtion (test) call.
//traces
// ...
// 10 updated
// onComplete

What do you see instead?
onComplete fires just before last update 
// traces
// ...
// onComplete
// 10 updated

Version 1.2.3

trying code 

  target.filter = [new BlurFilter(0, 0)];
  Actuate.effects(target, duration).filter(0, {blurX: 20, blurY: 20 });

and get null pointer exception in FilterActiator.initialize at line 

  start = Number (filter[propertyName]);

can be fixed, changing constructor,  from

  filter = (target as DisplayObject).filters [filterIndex]; 

to

  this.filter = (target as DisplayObject).filters [filterIndex]; 

thanks

The new haXe STD API method in haXe SVN Reflect.setProperty implements runtime 
setter handling on the javascript target. 

Actuate should use this method instead of Reflect.setField when using 
reflection so that the correct setter method is called while tweening.

Could you add onStart handler to GenericActuator? It's useful to know, when 
target STARTS update, mostly when delay is set. Thanks in advance

What steps will reproduce the problem?
1.Create a sprite ("container") and add it to the display list.
2.Create a sprite ("sp1") and add it to the container.
3.Create a bitmap and add it to "sp1".
4.Tween out "container".

What is the expected output? What do you see instead?
"container and its children will all fade out. Instead, onle one level deep 
seems to fade, anything nested further down does not fade out. 

What version of the product are you using? On what operating system?
Windows 7 64.

Please provide any additional information below.

THe sprite containing the bitmap does have a mouse listener but I do not think 
this is the issue.

@aholla

What steps will reproduce the problem?
1. Tween an element to alpha 0 (autoVisible is not changed from default)
2. Use "apply" to set the alpha back to 1.

What is the expected output? What do you see instead?
I expect to see the element at 100% alpha and visible.  Instead the element 
remains invisible.

What version of the product are you using? On what operating system?
actuate: [1.43]
hxcpp: [2.10]
neash: [1.0.3]
nme: [3.4.0]
OSX 10.8

Please provide any additional information below.
This is exactly how you would recreate the problem.
Actuate.tween(mc, 5, {alpha: 0}).onComplete(Actuate.apply, [mc, {alpha: 1}]);  
// doesn't show mc
Actuate.tween(mc, 5, {alpha: 0}).onComplete(Actuate.tween, [mc, 0.00001, 
{alpha: 1}]);  // does show mc

I have a loop with multiple onComplete functions and I'll get a warning in 
GenericActuator.as in Line 88:

MotionInternal::onComplete.apply (null, MotionInternal::onCompleteParams);


The warning is:

TypeError: Error #1010: Ein Begriff ist nicht definiert und hat keine 
Eigenschaften.
    at Function/<anonymous>()
    at Function/http://adobe.com/AS3/2006/builtin::apply()
    at com.eclecticdesignstudio.motion.actuators::GenericActuator/complete()
    at com.eclecticdesignstudio.motion.actuators::SimpleActuator/update()
    at com.eclecticdesignstudio.motion.actuators::SimpleActuator$/shape_onEnterFrame()

A simple try&error around line 88 will stop the warning, but I think a better 
fix would be appropriate

public function reflect(value:Boolean = true):GenericActuator
{
    motion_internal::reflect = true;
    motion_internal::special = true;
    return this;
}

maybe
    motion_internal::reflect = value;
    motion_internal::special = value;

?

What steps will reproduce the problem?
1. Add 3 elements with alpha 0
2. Apply fade in to alpha 1 in the 3 elements

What is the expected output? What do you see instead?
The first one appears but with not fluid fade in, the second one stays like 50% 
alpha and the third one stays almost transparent

What version of the product are you using? On what operating system?
Actuate 1.40 in Android (in Flash it works ok)

Please provide any additional information below.
The line y execute for each element:
Actuate.tween (_sprite, .75, { alpha: 1 });

It might be important that just before the fade in, there are another 3 
elements in those positions that fade out and dispose
Actuate.tween (_sprite, .5, { alpha: 0 } ).onComplete(dispose);

What steps will reproduce the problem?
// haXe but same behavior with AS
package ;

import com.eclecticdesignstudio.motion.Actuate;
import flash.Lib;
class Main 
{   
    static function main() 
    {
        var m:Main = new Main();
    }
    public function new()
    {
        Actuate.update(test, 1, [1],[10]).onComplete(function() trace('onComplete'));
    }
    function test(a)
    {
        trace(a + ' updated');
    }

}
// traces
// ...
// onComplete
What is the expected output? 
onComplete should fire last but there is a last funtion (test) call.
//traces
// ...
// 10 updated
// onComplete

What do you see instead?
onComplete fires just before last update 
// traces
// ...
// onComplete
// 10 updated

Version 1.2.3