This thread has been opened as Erel asked me to do so on thread http://www.b4x.com/android/forum/th...with-the-ime-library.14832/page-7#post-223401
In Portrait orientation, the Next/Done keys are not shown for EditText views (but the Return key is) when using the FOrder class: stevel05 states "The FOrder class only changes the order of the EditText view's entry, it should have no other effect on the views.". The coding from the FOrder class to set FOrder involves the use of "Refl.RunMethod2("setImeOptions",IME,"java.lang.int")" where IME=5 for all EditText views requiring 'Next' and IME=6 for the EditText view requiring 'Done'. The only EditText view requiring 'Done' is the last one in the "FieldOrder.Initialize(Array As Object(edtMap, edtAcross, edtUp), False)" command, namely edtUp.
NB this question was also asked in thread http://www.b4x.com/android/forum/threads/class-edittext-field-order.28002/page-2
A small Test project is attached which demonstrates this issue.
In Portrait orientation, the Next/Done keys are not shown for EditText views (but the Return key is) when using the FOrder class: stevel05 states "The FOrder class only changes the order of the EditText view's entry, it should have no other effect on the views.". The coding from the FOrder class to set FOrder involves the use of "Refl.RunMethod2("setImeOptions",IME,"java.lang.int")" where IME=5 for all EditText views requiring 'Next' and IME=6 for the EditText view requiring 'Done'. The only EditText view requiring 'Done' is the last one in the "FieldOrder.Initialize(Array As Object(edtMap, edtAcross, edtUp), False)" command, namely edtUp.
NB this question was also asked in thread http://www.b4x.com/android/forum/threads/class-edittext-field-order.28002/page-2
A small Test project is attached which demonstrates this issue.