I have an app which makes extensive use of Transition. It is a cpu simulator which animates the movement of data around and between registers over a bus.
On IOS devices and on the simulator it works fine, but on android the movement (which should be consistent obviously) sometimes follows the path detailed in the transition parameters and sometime is nothing like these values, appearing on screen to go on a dance.
Martin
Any ideas staffers?
here’s some of the code that runs correctly on IOS but randomly in Android:
transition.to(memory_buffer_register_label, {
delay = 0,
time = 500,
delta = true,
x = 0,
y = 70
})
transition.to(memory_buffer_register_label, {
delay= 500,
time = 1000,
delta = true,
x = 344,
y = 0
})
transition.to(memory_buffer_register_label, {
delay = 1500,
time = 1000,
delta = true,
x = 0,
y = -272
})
transition.to(memory_buffer_register_label, {
delay = 2500,
time = 1000,
delta = true,
x = 182,
y = 0})
hope someone can help, this is driving me potty.
Can you provide us more information?
What version of Corona SDK are you using?
What android devices and operating system is having the issues?
Hi Rob,
corona version 2013.2100
The machine I am testing on is a Galaxy Tab 3 7" tablet. I know the problem with Android is the range, but I cannot buy all of them to test. I have also tested on a Kindle fire with same problem.
The app is on the Google play store as a free download “Babbage Fetch”
thanks for your time.
Martin
Sorry didn’t say - Android 4.1.2
Can you put together a small sample app (build.settings, config.lua, main.lua with that code and the assets to make the transitions work, and try that on your device? Once you have that we can get you to file a bug report on it.
Rob
Rob,
I’ve been putting a skeleton together and it is getting there. The smallest version with just the config, build and a simple main which only has 4 transition.to gets its coordinates spot on for the Tab3 but as soon as I put more in it goes awry. I am narrowing down from the main app until the problem goes away then I will have the culprit. In the transition function there are only some constants for the coorinates as the path used does not vary, which is why I am so perplexed.
When I get to the point where the problem goes away I will upload what is left and where it goes wrong.
thanks
Martin
PS to anyone else who has an android device Id appreciate if you could download the free app from Google Play(Babbage Fetch) and just check if the animation goes wonky after a few goes. On the IOS device it is pixel perfect all the time.
Martin
Hi Rob,
I am narrowing it down, but it is very slippery and time consuming as the bug only manifests on device. I have an app now that works fine with repeated loops of the same transition statements then another that adds back in just a little bit of the intervening code and it all goes unpredictable again. I am trying to see which specific bits of code are causing the weirdness on Android but not IOS. I suspect it is a difference in the way transition is coded between the two platforms.
Martin
Any ideas staffers?
here’s some of the code that runs correctly on IOS but randomly in Android:
transition.to(memory_buffer_register_label, {
delay = 0,
time = 500,
delta = true,
x = 0,
y = 70
})
transition.to(memory_buffer_register_label, {
delay= 500,
time = 1000,
delta = true,
x = 344,
y = 0
})
transition.to(memory_buffer_register_label, {
delay = 1500,
time = 1000,
delta = true,
x = 0,
y = -272
})
transition.to(memory_buffer_register_label, {
delay = 2500,
time = 1000,
delta = true,
x = 182,
y = 0})
hope someone can help, this is driving me potty.
Can you provide us more information?
What version of Corona SDK are you using?
What android devices and operating system is having the issues?
Hi Rob,
corona version 2013.2100
The machine I am testing on is a Galaxy Tab 3 7" tablet. I know the problem with Android is the range, but I cannot buy all of them to test. I have also tested on a Kindle fire with same problem.
The app is on the Google play store as a free download “Babbage Fetch”
thanks for your time.
Martin
Sorry didn’t say - Android 4.1.2
Can you put together a small sample app (build.settings, config.lua, main.lua with that code and the assets to make the transitions work, and try that on your device? Once you have that we can get you to file a bug report on it.
Rob
Rob,
I’ve been putting a skeleton together and it is getting there. The smallest version with just the config, build and a simple main which only has 4 transition.to gets its coordinates spot on for the Tab3 but as soon as I put more in it goes awry. I am narrowing down from the main app until the problem goes away then I will have the culprit. In the transition function there are only some constants for the coorinates as the path used does not vary, which is why I am so perplexed.
When I get to the point where the problem goes away I will upload what is left and where it goes wrong.
thanks
Martin
PS to anyone else who has an android device Id appreciate if you could download the free app from Google Play(Babbage Fetch) and just check if the animation goes wonky after a few goes. On the IOS device it is pixel perfect all the time.
Martin
Hi Rob,
I am narrowing it down, but it is very slippery and time consuming as the bug only manifests on device. I have an app now that works fine with repeated loops of the same transition statements then another that adds back in just a little bit of the intervening code and it all goes unpredictable again. I am trying to see which specific bits of code are causing the weirdness on Android but not IOS. I suspect it is a difference in the way transition is coded between the two platforms.
Martin