One of my testers has a Galaxy S8 running Android 7.0
For phones that do not have dedicated hardware back/home/task buttons at the bottom of the phone, there is (what I believe it's called) a Navigation Bar, which displays the Back, Home and Task buttons on the bottom of the screen.
If the user chooses to hide the nav bar, when a B4A activity is shown, it displays all the way to the physical bottom of the display. And if the user then flicks up from the bottom, the nav bar appears transparently over the bottom of the activity.
But, the S8 (and maybe other Android 7.0 devices), allows the user to then Lock (or dock) the Nav bar at the bottom of the display. If they do this, then the nav bar is no longer transparent and visually blocks whatever was showing at the bottom of the activity. The activity is not automatically resizing to the new reduced screen space.
I did some testing, and yes the IME_HeightChanged event is triggered (if I add the IME lib and associated code to the activity). But I usually only needed to add IME for activities that had textboxes on them so they could deal with the screen resizing due to the keyboard being shown/hidden.
Does this mean I now have to add IME support to *EVERY* activity of every app from now on?
If so, is there some way B4A could automatically handle any HeightChanged events and automatically resize the contained views according to their specified anchor's (just like what it does when an activity is first shown)?
For phones that do not have dedicated hardware back/home/task buttons at the bottom of the phone, there is (what I believe it's called) a Navigation Bar, which displays the Back, Home and Task buttons on the bottom of the screen.
If the user chooses to hide the nav bar, when a B4A activity is shown, it displays all the way to the physical bottom of the display. And if the user then flicks up from the bottom, the nav bar appears transparently over the bottom of the activity.
But, the S8 (and maybe other Android 7.0 devices), allows the user to then Lock (or dock) the Nav bar at the bottom of the display. If they do this, then the nav bar is no longer transparent and visually blocks whatever was showing at the bottom of the activity. The activity is not automatically resizing to the new reduced screen space.
I did some testing, and yes the IME_HeightChanged event is triggered (if I add the IME lib and associated code to the activity). But I usually only needed to add IME for activities that had textboxes on them so they could deal with the screen resizing due to the keyboard being shown/hidden.
Does this mean I now have to add IME support to *EVERY* activity of every app from now on?
If so, is there some way B4A could automatically handle any HeightChanged events and automatically resize the contained views according to their specified anchor's (just like what it does when an activity is first shown)?