backKey handled by a closed stack? [solved]
Posted: Wed Mar 06, 2013 5:49 pm
Dear experts
I don't know if it's normal or not, but here's what happens in my app on Android
When the user presses a certain button in main stack A, main stack B opens. So far so good. If the user presses the hardware back key in main stack B, main stack B handles backKey and in that handler main stack B is closed, which causes main stack A to appear again. So far so good. But now, If the user presses the hardware back key again, backKey is still handled by main stack B, even after main stack B has been closed! Main stack A also has a backKey handler. I need main stack A to take over the handling of backKey once main stack B has been closed.
Any advice would be immensely appreciated.
Thanks
Gerrie
I don't know if it's normal or not, but here's what happens in my app on Android
When the user presses a certain button in main stack A, main stack B opens. So far so good. If the user presses the hardware back key in main stack B, main stack B handles backKey and in that handler main stack B is closed, which causes main stack A to appear again. So far so good. But now, If the user presses the hardware back key again, backKey is still handled by main stack B, even after main stack B has been closed! Main stack A also has a backKey handler. I need main stack A to take over the handling of backKey once main stack B has been closed.
Any advice would be immensely appreciated.
Thanks
Gerrie