Transition/Easing 2.0?

[jacques1]

I still get page not found whether in safari or firefox. Perhaps its a country based issue as I’m over here in Asia. So you’re able to DL build 1225?

[ingemar]

So am I :D   (I’m in Korea)

Looks like there are some propagation delays. I had the same issues, but was able to download about an hour ago…

[alexf]

Give it a bit of time, guys. The propagation can take a while sometimes.

alex

[alexf]

@paolo.longato

@jaques, I had exactly the same problem: lots of code and sporadic issues.  I managed isolate the problematic module and it turned out to be a synchronisation issue.  If you rely on one transition calling a function that erases some objects and these objects are being transitioned still, you might have issues ===>>> even if those transitions are supposed to start and end at the same time <<<===.  If you are synchronising transitions to end at the same time but one only is calling an onComplete function, make sure that this “master transition” ends 10 milliseconds after the others.  It worked for me and, however a long-shot, it might work for you.  In your case you have a duplicate object, so this one might still be around when you clean the scene or remove the object without cancelling the transition first.  I seem to remember that there is a new API that can tell you if an object is transitioning or not.  

I would love to try and reproduce the issue but I am a bit stretched at the moment.

Hope this helps.

@jacques1

You’re both right, I also tested stand-alone and it works fine. I also re-tested inside my code and it does still happen but not all the time, I noticed it only happens when the endText (which is an image in my code) somehow gets displayed (what appears to be duplicated on itself) as it is transitioning in scale. The problem could be other transitions before or after but it’s too complicated to get into here as there’s +25,000 lines of code.

Afraid I can’t give much more info to solve this other then this weird ‘duplicated code effect’ sporadically occurs after a transition’s onComplete happens on most of my transitions now. Appreciate the help anyways.

Will await the general fix for transitions2.0 and hopefully all my other transition2.0 woes will disappear too.

---

Okay checked another part (same duplicate problem), also tested it stand-alone and this one does seem to print the text in duplicate. Perhaps I’m doing the code wrong somehow?

local halfW = display.viewableContentWidth / 2

local halfH = display.viewableContentHeight / 2

local satellite=display.newGroup();satellite:translate( halfW, halfH)

sattxt=display.newText(satellite,“INITIATING SATELLITE LINKUP”, 0, 0, native.systemFont, 20)

sattxt.x=0;sattxt.y=0

sattxt.anime=transition.to( sattxt, { time=1000, alpha=0, transition=easing.continuousLoop,iterations=-1 } )

local yyLine=display.newLine(satellite,-halfW,0,halfW,0);yyLine.y=0;yyLine.width=2;yyLine.alpha=1

yyLine.anime=transition.to(yyLine,{time=500,y=halfH,onComplete=function()

    transition.to(yyLine,{time=500,y=-halfH,onComplete=function()

        transition.to(yyLine,{time=1000,y=0,transition =easing.outBounce, onComplete=function()

            if sattxt.anime~=nil then transition.cancel(sattxt.anime);print(“sattxt.anime cancelled”) end

        end})

    end})

end})

Help would be appreciated

Hi Paolo,

The issue should be fixed in 1225. Could you please confirm?

Thanks,

alex

[ingemar]

It looks like the double call to onComplete has been fixed with build #1225

[Stephen_Lewis]

For those who can’t download the latest daily build, try logging off the Corona website, then log back on and retry downloading again.

[paolo.longato]

@alexf – i am somewhere else entirely now, cannot download or even access my code.  untested pseudo code for my problem is:

local circle1 = display.newCircle(200, 200, 10)

local circle2 = display.newCircle(200, 200, 10)

local function removeObjects()

        display.remove(circle1); circle1 = nil

        display.remove(circle2); circle2 = nil

end

transition.to(circle1, "time = 500, xScale = 2, yScale = 2, onComplete = removeObjects ")

transition.to(circle2, “time = 500, xScale = 2, yScale = 2”)

It should throw an error with older version and not with 1225.  if that is the case, consider it solved.  and thanks a lot for looking into this.

[alexf]

@paolo.longato: did test with:

local circle1 = display.newCircle(200, 200, 30) local circle2 = display.newCircle(200, 400, 30) local removeObjects = function( event ) display.remove(circle1); circle1 = nil display.remove(circle2); circle2 = nil print( "Triggering onComplete" ) end transition.to(circle1, {time = 2000, xScale = 2, yScale = 2, onComplete = removeObjects } ) transition.to(circle2, {time = 2000, xScale = 2, yScale = 2} )

and it works perfectly in 1225.

alex

[paolo.longato]

@alexf question is: does it break in 1219?

[jacques1]

Build 1225 seems to have resolved the issues and so far from what I can tell the transitions seem to work fine now, no more double calls after onComplete.

@paolo: I still had the errors occur in 1219, so you should definitely get 1225.

[paolo.longato]

@jaques1, yes.  My question was (given that I am away from my development computer), did I isolate the “correct” problem in the first place with my pseudo-code written from a cafe’ in the middle of Copenhagen (while drinking capuccino and enjoying the sunny day)?  If so I am happy (doubly happy as it feels good to solve a problem while actually not working ). 

I also remember getting warning messages saying something along the lines of: attempt to set alpha outside boundaries (and a very small negative number).  I have no idea what triggers it but I assume it was transitions (only a transition could be capable of setting alpha on objects at funny levels like -0.18334323e-5).  If “stopping time” issues are fully resolved in 1225 I bet I will not see that message anymore either .

[jonjonsson]

That alpha warning I have seen when transitioning alpha to 0 or 1 with a bouncing transition. Its kind of annoying. 

[paolo.longato]

point in case: in 1225 you should not see it if the stopping time problem is resolved. 

@jonjonsson

That alpha warning I have seen when transitioning alpha to 0 or 1 with a bouncing transition. Its kind of annoying. 

[rob]

The engineers have identified the download problem are working on fixing it.  It seems to only be affecting some people, hopefully this will be resolved shortly. 

When it is, I encourage everyone to pick up daily build 1225 or later as 1225 has the latest fixes to handle the nil object and time default issues.  If you do continue to post issues about Transitions 2.0 please make sure to include your build number and any details that will help us track the problem down.

EDIT: and right as I click the save button, I get a note from the engineers that the download problem should be fixed. 

Thanks

Rob

[searchm]

It would be super nice to have a method that checks globally if an object is currently animated. like:

if object:isanimated() then … end

without having to set the transition to a variable. just my 2 cent.