Use Case
The keyboard currently provides four cursor movement actions (up, down, left, right) which send D-pad KeyEvents and can be placed in custom layouts via !icon/action_up|!code/action_up etc. However, there is no way to move the cursor by larger jumps:
Page Up / Page Down — quickly navigating long documents, notes, code files, or terminal apps (e.g. Termux) without hammering the up/down arrows
Home / End — jumping to the start or end of the current line, one of the most common editing motions when writing or coding on mobile
These are especially valuable for custom layouts aimed at text editing, SSH/terminal use, and external-display productivity setups. Holding a repeatable arrow key is a poor substitute for a single deliberate jump.
Proposal:
Add four new actions to the action registry — e.g. page_up, page_down, home, end — implemented the same way as the existing arrow actions, but sending KEYCODE_PAGE_UP (92), KEYCODE_PAGE_DOWN (93), KEYCODE_MOVE_HOME (122), and KEYCODE_MOVE_END (123) respectively. This would automatically make them available both as action-bar actions and as layout keys via the !icon/action_X|!code/action_X keyspec syntax, with no changes needed to the layout format itself.
References:
Existing arrow actions in java/src/org/futo/inputmethod/latin/uix/actions/ (Registry.kt)
Android KeyEvent constants: KEYCODE_PAGE_UP/DOWN, KEYCODE_MOVE_HOME/END
Use Case
The keyboard currently provides four cursor movement actions (up, down, left, right) which send D-pad KeyEvents and can be placed in custom layouts via !icon/action_up|!code/action_up etc. However, there is no way to move the cursor by larger jumps:
Page Up / Page Down — quickly navigating long documents, notes, code files, or terminal apps (e.g. Termux) without hammering the up/down arrows
Home / End — jumping to the start or end of the current line, one of the most common editing motions when writing or coding on mobile
These are especially valuable for custom layouts aimed at text editing, SSH/terminal use, and external-display productivity setups. Holding a repeatable arrow key is a poor substitute for a single deliberate jump.
Proposal:
Add four new actions to the action registry — e.g. page_up, page_down, home, end — implemented the same way as the existing arrow actions, but sending KEYCODE_PAGE_UP (92), KEYCODE_PAGE_DOWN (93), KEYCODE_MOVE_HOME (122), and KEYCODE_MOVE_END (123) respectively. This would automatically make them available both as action-bar actions and as layout keys via the !icon/action_X|!code/action_X keyspec syntax, with no changes needed to the layout format itself.
References:
Existing arrow actions in java/src/org/futo/inputmethod/latin/uix/actions/ (Registry.kt)
Android KeyEvent constants: KEYCODE_PAGE_UP/DOWN, KEYCODE_MOVE_HOME/END