Transition.to fault or user error?

stubones99 · May 18, 2013, 3:25pm

I am using transition.to to move a small pointing finger across the bottom of the screen (to show users how they navigate the app).

Here is the code I use:

&nbsp; &nbsp; &nbsp; &nbsp; local tpf = display.newImage("tiny pointing finger.png",50,50) &nbsp; &nbsp; &nbsp; &nbsp; tpf.x = 300 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; -- set starting location &nbsp; &nbsp; &nbsp; &nbsp; tpf.y = 455 &nbsp; &nbsp; &nbsp; &nbsp; tpf.alpha = 1 &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; local function tpfDone(event) &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; tpf.alpha = 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; tpf:removeself() &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; end &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; transition.to(tpf, {time=2000, x=20, alpha=0, transition=easing.inExpo, onComplete=tpfEnd} ) &nbsp;

The function is to move the hand slowly at first from the right side of the screen to the left, speeding up as it goes (inExpo at work). It is also going to fade the alpha from 1 to zero along the way.

The error reported on the simulator output window is as follows:

Windows simulator build date: Apr &nbsp;3 2013 @ 13:54:22 Copyright (C) 2009-2013 &nbsp;C o r o n a &nbsp; L a b s &nbsp; I n c . &nbsp; &nbsp; &nbsp; &nbsp; Version: 2.0.0 &nbsp; &nbsp; &nbsp; &nbsp; Build: 2013.1076 waiting for connection... connected waiting for debugger initialization program started Copyright (C) 2009-2013 &nbsp;C o r o n a &nbsp; L a b s &nbsp; I n c . &nbsp; &nbsp; &nbsp; &nbsp; Version: 2.0.0 &nbsp; &nbsp; &nbsp; &nbsp; Build: 2013.1076 waiting for connection... connected waiting for debugger initialization program started WARNING: Attempt to set object.alpha to 1.00001 which is outside valid range. It &nbsp;will be clamped to the range [0,1] WARNING: Attempt to set object.alpha to -2.07261e-005 which is outside valid ran ge. It will be clamped to the range [0,1] WARNING: Attempt to set object.alpha to 1.00001 which is outside valid range. It &nbsp;will be clamped to the range [0,1] WARNING: Attempt to set object.alpha to -2.07261e-005 which is outside valid ran ge. It will be clamped to the range [0,1] &nbsp;

The warnings are that the alpha is set out of range by some exponential number. I suspect this is a problem of the inExpo function…

OK, I know it is a warning and no one but us will know it happened and Corona fixed it by clamping the number to the appropriate values. Still this is a “problem” that does not happen without the inExpo feature, so probably that is the culprit…

AND…

Corona still has not fixed the problem with the windows simulator starting TWICE (once as an android, and then restarting as an IOS device)…

Any suggestions (other than don’t do that?).

Thanks!
stu