I don't know if this is a bug or Android "gotcha", but this caused me a bit of grief until I finally figured out the problem.
Activity1 (not "full screen")
Activity2 ("Full screen")
1) Start the app (Activity1) in portrait or landscape
2) Start Activity2 (such as a setup activity, whatever)
3) Rotate the device to change the orientation
4) Exit the 2nd (full screen) activity to return to the 1st (not full screen) activity
Result: Activity.Height and Num%Y return incorrect height because it is not initially accounting for the notification bar at the top of the screen (because for a brief moment it is not there). It does eventually appear and then it shifts stuff down, but then this causes views to be cut off at the bottom. And in my case now of using %X and %Y to size and move all of the views, it causes buttons to be positioned wrong and overlap.
My (probably obvious) solution of course was to remove the "Full screen" option on Activity2. It was the only activity set with that option in my app and in fact was an accident when I first started designing the app and I never noticed until this happened.
Just an FYI. If this is a B4A bug, it should be addressed. If it is an Android thing, then maybe my lesson will help others.
Activity1 (not "full screen")
Activity2 ("Full screen")
1) Start the app (Activity1) in portrait or landscape
2) Start Activity2 (such as a setup activity, whatever)
3) Rotate the device to change the orientation
4) Exit the 2nd (full screen) activity to return to the 1st (not full screen) activity
Result: Activity.Height and Num%Y return incorrect height because it is not initially accounting for the notification bar at the top of the screen (because for a brief moment it is not there). It does eventually appear and then it shifts stuff down, but then this causes views to be cut off at the bottom. And in my case now of using %X and %Y to size and move all of the views, it causes buttons to be positioned wrong and overlap.
My (probably obvious) solution of course was to remove the "Full screen" option on Activity2. It was the only activity set with that option in my app and in fact was an accident when I first started designing the app and I never noticed until this happened.
Just an FYI. If this is a B4A bug, it should be addressed. If it is an Android thing, then maybe my lesson will help others.
