You marked it for “investigation”.
The sample code I put at the top of the post will show it. Whenever the square comes back to 0 (start) position it warps to for a single frame and then goes back to 0 to start the transition.
You marked it for “investigation”.
The sample code I put at the top of the post will show it. Whenever the square comes back to 0 (start) position it warps to for a single frame and then goes back to 0 to start the transition.
I’ve reported this as a bug case and asked the engineers for prompt investigation. Case is #29900.
Hi there, any news about this issue? I have similar problem with public release 2013.2100 on try to apply a scale transition loop
local circle = display.newCircle( display.contentCenterX, display.contentCenterY, 50 )
transition.to( circle, {xScale=1.05, yScale=1.05, time=1000, iterations=-1, transition=easing.continuousLoop} )
Hi @martinellid,
This should be fixed in the upcoming public release, which isn’t too far away now.
Best regards,
Brent
Thank you Brent!
The latest build has fixed this problem in relation to rotation etc, but it seems to have introduced a problem with the x value of the object
this demonstrates the problem
local circle = display.newCircle( 512, 100, 50 )
circle.anchorX, circle.anchorY = 0.5, 0.5
circle:setFillColor(1,0,0,1)
circle.x = 512
transition.to( circle, {time = 5000, x = 712 , y = 50, transition = easing.continuousLoop, iterations = -1} )
the x value in the transition = the x value that I want - half the width of the screen.
something is subtract half the screen width. in the above example the circle should goto the right but it goes to the left.
this is with build 2014.2179
Hi @samwit,
In your code, where does the circle x actually begin? 512 or 712? And you say it starts moving to the left, not to the right? Can you put a starting delay on the transition and then confirm its starting x position?
Thanks,
Brent
the code clearly shows it begins at 512
here it is with delay so you can see it starts there
local circle = display.newCircle( 512, 100, 50 )
circle.anchorX, circle.anchorY = 0.5, 0.5
circle:setFillColor(1,0,0,1)
circle.x = 512
transition.to( circle, {time = 5000, x = 712 , y = 50, delay = 1000, transition = easing.continuousLoop, iterations = -1} )
Thanks Brent appreciate it.
Hello @Brent, i was very happy with the new public release and I immediately installed. But i was very disappointed when i saw that the transitions bug was not resolved. Is there any hope of being able to fully use the transitions?
Hi @martinellid,
This bug should be fixed in the latest public build. Are you seeing otherwise?
Brent
Hi @Brent, yes i seeing otherwise. This little piece of code does not work as I would expect:
local circle = display.newCircle( display.contentCenterX, display.contentCenterY, 50 )
transition.to( circle, {xScale=1.05, yScale=1.05, time=1000, iterations=-1, transition=easing.continuousLoop} )
and certainly behaves very differently from the same code without transition=easing.continuousLoop.
Hi @martinellid,
I see your point, and I’ve bumped this with engineering. I thought it was fixed but apparently it’s not, at least in this specific use case.
Brent
Thank you Brent
Hi there, any news about this issue? I have similar problem with public release 2013.2100 on try to apply a scale transition loop
local circle = display.newCircle( display.contentCenterX, display.contentCenterY, 50 )
transition.to( circle, {xScale=1.05, yScale=1.05, time=1000, iterations=-1, transition=easing.continuousLoop} )
Hi @martinellid,
This should be fixed in the upcoming public release, which isn’t too far away now.
Best regards,
Brent
Thank you Brent!
Hello @Brent, i was very happy with the new public release and I immediately installed. But i was very disappointed when i saw that the transitions bug was not resolved. Is there any hope of being able to fully use the transitions?
Hi @martinellid,
This bug should be fixed in the latest public build. Are you seeing otherwise?
Brent