You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(1) Am I creating the timelines correctly? all of my timelines are generally created this way.
//****************************************************************************************************************
public static Timeline doSexyZoomScaleIn(ImageLayerContainerLocal ilc,float delay){
Timeline animationTimeline = Timeline.createParallel().beginParallel()
.push(Tween.from(ilc, TweenEngineAccessorContainer.SCALE, 400.0f).target(5f, 5f).ease(TweenEquations.easeOutBack))
.push(Tween.to(ilc, TweenEngineAccessorContainer.ALPHA, 200).target(0.4f).ease(TweenEquations.easeOutBack))
.end();
return animationTimeline;
}
//********************************************************************************************************
(2) I see you have a fix for this bug 2 years ago, and switching to 6.3.3 really made a big difference in the frequency the issues occurs but It did not stop it. Is it something I'm doing that may cause the issue to occur?
I'm also attaching callbacks so I can trigger events in my app. any insight will be greatly appreciated, even if it to point me to where the timelines are managed in the api and I'll try fixing it myself(I have tried).
The text was updated successfully, but these errors were encountered:
I'm using Google PlayN(Java)
(1) Am I creating the timelines correctly? all of my timelines are generally created this way.
//****************************************************************************************************************
public static Timeline doSexyZoomScaleIn(ImageLayerContainerLocal ilc,float delay){
Timeline animationTimeline = Timeline.createParallel().beginParallel()
.push(Tween.from(ilc, TweenEngineAccessorContainer.SCALE, 400.0f).target(5f, 5f).ease(TweenEquations.easeOutBack))
.push(Tween.to(ilc, TweenEngineAccessorContainer.ALPHA, 200).target(0.4f).ease(TweenEquations.easeOutBack))
.end();
return animationTimeline;
}
//********************************************************************************************************
(2) I see you have a fix for this bug 2 years ago, and switching to 6.3.3 really made a big difference in the frequency the issues occurs but It did not stop it. Is it something I'm doing that may cause the issue to occur?
I'm also attaching callbacks so I can trigger events in my app. any insight will be greatly appreciated, even if it to point me to where the timelines are managed in the api and I'll try fixing it myself(I have tried).
The text was updated successfully, but these errors were encountered: