Explicit keyboard action for numeric fields and consistent native Next navigation

[DurankGts]

Please provide a documented way to configure the keyboard action independently of the input constraint, e.g. NUMERIC with NEXT or DONE.

Android already supports TYPE_CLASS_NUMBER combined with IME_ACTION_NEXT. CN1’s InPlaceEditView selects NEXT when a next field exists, but a DoneListener overrides it.

On iOS, NumberPad has no Return key, so NEXT requires a native input accessory. CodenameOne_GLViewController already implements a Next/Done toolbar for numeric keyboards under certain conditions, with an iPad exclusion.

Please clarify the supported configuration and make this behavior consistent for numeric fields on Android, iPhone and iPad. The requested iOS solution is a native keyboard accessory managed by the port.

Acceptance criteria:

Numeric input remains numeric.
NEXT moves to the configured next editable field.
DONE finishes editing on the last field.
Navigation works in portrait and landscape.
Document how DoneListener and toolbar visibility affect the selected action

[shai-almog]

Thanks, we're looking into this in #6217.

Once it's in you would be able to set the action explicitly on Android and iOS, with any constraint:

field.putClientProperty("nextButton", Boolean.TRUE);  // or "doneButton"

nextButton moves to the next field without firing the Done listener; doneButton ends editing and fires it. Fields that set neither are unchanged.

On iOS the number pad's Next/Done toolbar now stays in landscape, and shows on iPad when either property is set. The developer guide gets a section with the full rules.