Hi,
I was testing transitions for a client, and I think I found out what was the trouble.
First : This is not about this topic Android Client : Bug with the last Out Transition of a region. It’s something else.
Second : how to reproduce :
- Create two regions
- Create two widgets for each region (to avoid the trouble where you have only one item in a region, and an out transition)
- Add One fade in transition for the first widget of each region
- Add an Fly Out transition for one of the region
- Add a Fade Out transition for one of the region
- Run the layout
- The In transition is good
- The Out transition of the Fly Out is quicker than the Fade out. It has enough time to try to reboot the region, than it stops after 0.5s.
- The layout reboots
What’s happening is that the fly transition is sometimes quicker, sometimes longer than the fade out transition. There is no trouble when there are two fade out transition, but with two fly out sometimes it does.
You can change the fade out duration to test. For me, when I go under 1170 seconds for the fade out transition, then the fade out is longer than the Fly.
This bug might be because the fade out must be really difficult to time, but the current solution is not good enough.
I can provide a video and a template to show you the problem.
I hope we can find what’s going on, so maybe there will be a fix for the next update. For now, we are only using the Fade Transitions, but we really want to use the Fly.
Rodolphe from A2Display