By default, line 7 in main.lua is set to ‘true’. This tells the example to automatically cycle through the focused fields so you can watch how the devices handle panning and off-screen fields. Turn it to false if you want to interact with the example.
local enableAutoFocus = true
Please note: On iOS, if a field slides offscreen, you can access it by setting the keyboard focus first to ‘nil’, then to the field you want to access. On android you do not want to set the focus to ‘nil’ or the keyboard will wiggle a bit which is ugly.
Since you are using the method were we scroll the active scrollView into where it’s just above the keyboard, you should be able to know which field that is. Lets say its a field named emailField. Then it’s vertical location would be found at:
I’m not sure if this is a bug report or if I should submit this as a feature request, but when I use: CoronaWindowMovesWhenKeyboardAppears=true
it works fine with the default keyboard, but some of my users have reported that the window does not shift up when they use their own custom keyboards like “Swift Key” or “Gboard” on iOS 9. .
CoronaWindowMovesWhenKeyboardAppears is an experimental feature. If it works for you great, if not, then we suggest finding alternate ways to move your native input objects. They can be inserted into groups and the whole group now.
There are no plans to go back and work more on this auto-panning feature.
Thanks for the quick response Rob. Just to clarify there is still no way to get the keyboard height at the moment right? It’s kind of a guessing game on where to move the native input object?
Since you are using the method were we scroll the active scrollView into where it’s just above the keyboard, you should be able to know which field that is. Lets say its a field named emailField. Then it’s vertical location would be found at:
I’m not sure if this is a bug report or if I should submit this as a feature request, but when I use: CoronaWindowMovesWhenKeyboardAppears=true
it works fine with the default keyboard, but some of my users have reported that the window does not shift up when they use their own custom keyboards like “Swift Key” or “Gboard” on iOS 9. .
CoronaWindowMovesWhenKeyboardAppears is an experimental feature. If it works for you great, if not, then we suggest finding alternate ways to move your native input objects. They can be inserted into groups and the whole group now.
There are no plans to go back and work more on this auto-panning feature.
Thanks for the quick response Rob. Just to clarify there is still no way to get the keyboard height at the moment right? It’s kind of a guessing game on where to move the native input object?