Why does Corona not support a xScale/yScale equal to 0(zero)

Audio and Graphics
#1

I’m currently scaling a few objects in realtime (on frame updates) using sine and cosine to determine their scale.

This means that at some point the scale will equal 0(zero). I do want the objects to not be visible when the scale goes to 0(zero), so using sine and cosine is just what I want.

Now the issue is that whenever the scale gets set to zero I get a bunch of warnings like this:

WARNING: Cannot set y-scale property of display object to zero.

I assume by the warnings that the scale is not actually getting set to zero, but its still not visible (probably because it has been set to a really small number on the previous frame), so I’m basically getting the visual behaviour I want, but I also get all those warnings, which basically make my logs unreadable.

So… is there any reason why Corona cannot just scale things to zero? I mean scaling something to zero is not an issue with any other tool/framework I’ve used.

If there is some legacy reason that it cannot take a scale of zero that would be unfortunate, however I know that sort of thing happens and I’m perfectly fine with that. But would be really happy if there was a way to have Corona not pump out warnings I don’t want to see. In this case Is there some build flag or something I can set to change the Warning settings?

Thanks again!

#2

I’ve not seen the code, but if I were to guess, I would suspect it’s a “Divide by Zero” clause and we simply can’t do it because it’s mathematically impossible. This should just be a warning and shouldn’t be an issue.

Rob

#3

why don’t you use .isVisible=false if xScale goes < 0.01 for example?

#4

I’ve not seen the code, but if I were to guess, I would suspect it’s a “Divide by Zero” clause and we simply can’t do it because it’s mathematically impossible. This should just be a warning and shouldn’t be an issue.

Rob

#5

why don’t you use .isVisible=false if xScale goes < 0.01 for example?