Was going to say its usually with transitions...

I believe its rounding errors in C that produce the extra 0.001 and there is not much that can be done. The error is unnecessary I believe as Corona will automatically reset the value to 1.

Are all the warning messages coming from transition.to statements? I can see where math rounding errors could produce the warning messages. If that's the source of all the warnings I think the values should be capped internally without the warning message.

-Tom

Hey Tom

I discussed this with Carlos / Eric or someone months back. I believe you can generate the warning error if you manually set alpha to out of the range ( used to be able to, not tried lately )

But yeah its usually the transitions causing the warning message. I think they are capped at 0 and 1 but the message appears to inform you of the capping. Its not an issues as such, I dont mind it, but yeah it can fill up a terminal window if you have lots of transitions firing at once.

Rounding errors are nothing new though and not a direct Corona bug so I left it there.

math.floor or checking newAlpha > 1 works as well for manual functions

Matthew,

I know about the warnings if you manually set the alpha value out of range but was curious if it was happening if you manually set it to 0 or 1.

Thanks,
-Tom

Manually setting 0 or 1 directly doesn't generate the warning message

I was playing with some transitions and couldn't generate the alpha warning message. I tried going from alpha 0 to 1 and 1 to 0 with some odd times (e.g. 333 msec). Anyone have a case that shows the message?

-Tom

Also tried and cant now get the message.

If I see it again will post the code

I have to agree that this warning message is quite annyoing since it fills the entire console window -is there a way to disable it? I don't want to slow down my code with unneccessary if...then statements just to avoid this warning :-(

EDIT: *sigh* same with xScale and yScale -_-

It is definate the transition.to function. The funny thing is that it isn't cosistantly reproduceable. Sometimes it shows up, sometimes not. At first I thought it is the image but then it doesn't happen all the time. Weird bug.

Its just C rounding errors, language based and Corona takes care of it.

The warning is annoying but nothing to worry about.

If this warning is fired on the device too, then it will have an effect on teh framerate, the more warnings, the more messages.

I find that the warning messages show up if I use an easing function that goes in and out of the normal bounds.

See this for the easing that go out of the bounds, and can make alpha be > 1 and < 0.

http://developer.anscamobile.com/code/more-easing

The problem can be reproduced if you change the alpha property in a transition.to that is called by a performWithDelay. Doing the transition.to without the performWithDelay does not cause the warning. It's on our to-do list to be fixed.

Here is the code that shows the problem:

1
2
3
4
5
6
7
8
9

local function test()
        t = display.newText( "Testing Alpha in Transition.to", 0, 0, nil, 20 )
        t.alpha = 1
        t:setTextColor( 255, 255, 255 )
        
        transition.to( t, {time = 700, alpha = 0} )
end
        
        timer.performWithDelay( 100, test )