LiveCode Forums

I have a somehow difficult to describe problem on Android hardware , that doesn't show on iOS standalone nor on development (Mac), probably because a better speed of execution.
It is difficult to pin point this navigation problem because of so many lines of code that get run when moving form stack to stack.

I have, let's say, a main Stack "A" which has 2 substacks, "B" and "C".
- "A" is always opened and I show/hide it at need
- "B" and "C" are closed when moving from one to the other

1) From "B", I go to "C" ("A" is hidden)
2) from "C" I go to "A", show "A" and then close "C"
3) from "A" I go to "B" and hide "A"

Action 3) is where there is a problem: navigation is correct, but before showing "B", the phone screen shows "C" for around half a second (my Android phone is pretty slow).
"C" should be closed (and it is, I checked with openstacks) but still will show in between for a short time.
No openstack or preopenstack is run on "C"
For what I can tell in the "Message Watcher", substack "C" is not involved what's so ever in action 3

What could possibly cause what looks like a refresh problem?
Thanks

Since only one window is available on mobile, you don't need to close or hide any stacks. The toplevel stack will always be the one you see.

To simulate this during development, just set the size and position of all stacks to the same coordinates. They will all remain open but you'll only see the top one.

Yew, i am aware of this.
My App is for Android and iOS (cell and tablets) and there are subtle differences between Android and iOS on handling the UI navigation, that somehow hiding substacks solve.
I think I need more info on the differences of navigation between the two platform (if any or if there are yet unsolved bugs) when there are visual effect, lock screen, close stack ,etc involved