Error after update to CoronaSDK-2013.1208

Solar2D Daily Builds and Public Releases
#41

don’t think so, at least not in the files to be considered.

did you check a gotoScene inside an onComplete listener?

 local listener = function(obj) local options = { params = { mapIdx = t.idx, } } storyboard.gotoScene("scripts.scenes.levelMapScene", options) end transition.to(t[1], {delay=0, time=200, xScale=1.1,yScale=1.1}) transition.to(t[2], {delay=0, time=200, xScale=1.1,yScale=1.1}) transition.to(t[1], {delay=200, time=200, xScale=1,yScale=1}) transition.to(t[2], {delay=200, time=200, xScale=1,yScale=1, onComplete=listener})
#42

I store transitions in a table attached to the display object and have a generic transition callback function which cancels and nils them out onComplete.
 

local function transOnComplete( obj ) if (obj and obj.trans) then         for i=1, #obj.trans do             transition.cancel( obj.trans[i] )             obj.trans[i] = nil         end         obj.trans = nil     end end local myRect = display.newRect(100,100,50,50) local function myRectTransOnComplete( myRect )     transOnComplete( myRect )     --[[Here I would sometimes call storyboard.gotoScene]] end myRect.trans = {} myRect.trans[1] = transition.from( myRect, {      time = 500,     delay = 2000,     alpha = 0,     onComplete = myRectTransOnComplete })  

However, running this extracted example doesn’t seem to cause the error.
I do also sometimes call storyboard.gotoScene from within the transition onComplete, but I don’t see why this would cause a problem.

#43

Hi everyone,

The daily build 1225 that went out today should fix all the issues reported here. Would you please be so kind to check if everything runs ok?

Thanks for your patience on this!

#44

Thanks alexf, seems to have done the trick for me.
What was causing it?

#45

works for me, please explain yourself…

#46

Hey martin189, juliusbangert,

As Walter posted above on the thread, it had to do with a race condition happening in the internal transition table. Altering a transition while iterating the internal transition table was the culprit.

alex

#47

don’t get that, but thanks anyway

#48

still error using build 1225, error:

untime error
?:0: attempt to index field ‘?’ (a nil value)
stack traceback:
        [C]: ?
        ?: in function <?:498>
        ?: in function <?:218>

#49

mlhdyx: also happening with the current daily build?

Thanks,

alex

#50

Yes ,start a new transition in onComplete.

#51
  1. I tried lots of version of daily build, 1210, 1214, 1225, and the last 1260.

I don’t want to switch to the 2xxx version right now, so I just choose the 12xx versions to test.

  1. it’s a common way that I created the new transition in onComplete,

like to implement a continuous rotate.

demo code:

function Class:foo()

transition.to(cursor, {time=1000, rotation=360,onComplete=self})

end

function  Class:onComplete(object)

…

        transition.to(object, {time=1000, rotation=object.rotation+360, onComplete=self})

end

#52

still error using build 1225, error:

untime error
?:0: attempt to index field ‘?’ (a nil value)
stack traceback:
        [C]: ?
        ?: in function <?:498>
        ?: in function <?:218>

#53

mlhdyx: also happening with the current daily build?

Thanks,

alex

#54

Yes ,start a new transition in onComplete.

#55
  1. I tried lots of version of daily build, 1210, 1214, 1225, and the last 1260.

I don’t want to switch to the 2xxx version right now, so I just choose the 12xx versions to test.

  1. it’s a common way that I created the new transition in onComplete,

like to implement a continuous rotate.

demo code:

function Class:foo()

transition.to(cursor, {time=1000, rotation=360,onComplete=self})

end

function  Class:onComplete(object)

…

        transition.to(object, {time=1000, rotation=object.rotation+360, onComplete=self})

end