MobileOrientation problem
Posted: Tue Nov 21, 2017 3:30 pm
The problem, the short version ....
I have two substacks where I have put:
"mobileSetAllowedOrientations portrait, Landscape left"
one is in layout "portrait mode" and one is in layout "Landscape mode" so I can switch between them by tilting the phone. (Close one stack open another etc etc). Each subStack is a single card stack with no buttons (the user have to use the hardware button to go back).
The purpose is to show a list in portrait mode and by tilting the phone, open another subStack with a more detailed list in landscape mode.
so far so good...
Now to the problem!
When I close the subStack and return to my mainStack (this is always done from the subStack which is in portrait mode), I set both: "mobileSetAllowedOrientations portrait" and "mobileLockOrientation" on the "MainCard" OpenCard handler.
If I then tilt the phone, the "landscape" subStack opens up, which I think should not be possible.
I use both: "set the destroyStack of this stack to true" and "close stack", but still the subStack/s seems to be active in some way.
Why?
Suggestions anyone?
///Peter
I have two substacks where I have put:
"mobileSetAllowedOrientations portrait, Landscape left"
one is in layout "portrait mode" and one is in layout "Landscape mode" so I can switch between them by tilting the phone. (Close one stack open another etc etc). Each subStack is a single card stack with no buttons (the user have to use the hardware button to go back).
The purpose is to show a list in portrait mode and by tilting the phone, open another subStack with a more detailed list in landscape mode.
so far so good...
Now to the problem!
When I close the subStack and return to my mainStack (this is always done from the subStack which is in portrait mode), I set both: "mobileSetAllowedOrientations portrait" and "mobileLockOrientation" on the "MainCard" OpenCard handler.
If I then tilt the phone, the "landscape" subStack opens up, which I think should not be possible.
I use both: "set the destroyStack of this stack to true" and "close stack", but still the subStack/s seems to be active in some way.
Why?
Suggestions anyone?
///Peter