Summary
The built-in on-screen keyboard has no Backspace key, so text can be typed into Flash content but not corrected.
Details
The tags currently defined in app/src/main/res/layout/keyboard.xml are:
1–0, Q–M, CTRL, ALT, SPACE, LEFT, UP, DOWN, RIGHT, plus kb and cm.
key_tag_to_key_descriptor() in src/keycodes.rs accepts exactly the same set, so there is currently no tag that could map to Backspace.
The hardware keyboard path already handles it, though — android_key_event_to_ruffle_key_descriptor() maps Keycode::Del to NamedKey::Backspace. So a Bluetooth keyboard works fine; only the on-screen keyboard is missing the key. (Enter and Shift appear to be absent as well.)
Question before opening a PR
The change looks small: one more match arm in keycodes.rs plus a button in the layout. Before spending time on it, I'd like to check the intended direction, because the README TODO lists:
[ ] Ability to show the built-in virtual keyboard (softinput), for text input
If the system soft keyboard is the planned route for text input, adding keys to the custom overlay may not be what you want, and I'd rather not send a PR that pulls the other way.
Happy to prepare the change if it's welcome — just let me know which approach you'd prefer.
Observed on 0.260720 (F-Droid).
Summary
The built-in on-screen keyboard has no Backspace key, so text can be typed into Flash content but not corrected.
Details
The tags currently defined in
app/src/main/res/layout/keyboard.xmlare:1–0,Q–M,CTRL,ALT,SPACE,LEFT,UP,DOWN,RIGHT, pluskbandcm.key_tag_to_key_descriptor()insrc/keycodes.rsaccepts exactly the same set, so there is currently no tag that could map to Backspace.The hardware keyboard path already handles it, though —
android_key_event_to_ruffle_key_descriptor()mapsKeycode::DeltoNamedKey::Backspace. So a Bluetooth keyboard works fine; only the on-screen keyboard is missing the key. (EnterandShiftappear to be absent as well.)Question before opening a PR
The change looks small: one more match arm in
keycodes.rsplus a button in the layout. Before spending time on it, I'd like to check the intended direction, because the README TODO lists:If the system soft keyboard is the planned route for text input, adding keys to the custom overlay may not be what you want, and I'd rather not send a PR that pulls the other way.
Happy to prepare the change if it's welcome — just let me know which approach you'd prefer.
Observed on 0.260720 (F-Droid).