| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
There is no way to type letters on the pin layout, the indication are
decoration only.
Use the E.161 standard.
|
|
The layout is used for phone number and datetime input boxes as well as
some numbers.
It is easier to use when the full numeric layout is not needed.
|
|
Shows a NumPad depending on preference:
Never/Landscape/Always
|
|
Avoid dropping some keys on crowded layouts.
|
|
Keep track of end-of-sentence characters while typing and automatically
enable shift when appropriate.
The last few characters just before the cursor need to be queried in
some cases: Begin of input, cursor has moved or text is deleted.
This might have a performance cost.
This normally only enable shift but it also needs to disable shift when
the cursor moves.
|
|
The "loc " prefix for predefining a place for an "extra key" was broken
since 31d6a70.
The FLAG_LOCALIZED flag cannot be used anymore, as adding it to any key
would turn it into a different key that wouldn't be recognized by parts
of the code comparing the keys (placing the extra keys).
Add an other layer in KeyboardData to store such informations.
|
|
|
|
Layouts no longer need to mention every localized keys and dead keys.
They are now placed automatically starting from the second row on the
bottom-right corner.
The "loc " prefix is not removed to still be able to define a more
optimal and consistent placement for some extra keys (eg. 'ß' near 's').
Programming layouts no longer need to place every dead keys.
|
|
The "closest key" logic must be careful not to reveal keys removed by a
modifier.
Must check [_handler.onPointerSwipe] for every candidate values.
[selected_value] is changed back to [selected_direction].
This adds a new bug: When the direction change, the selected value might
not change but a vibration will be triggered anyway.
|
|
getAtDirection was too hard to maintain and might contain bugs.
Change slightly the meaning of directions and implement a the nearest
key calculation as a loop.
|
|
|
|
fix a direction
|
|
Android 6 uses Java 1.7, the only incompatible feature in use was
lambdas.
|
|
Modifiers can temporarily remove a key from the layout by returning
'null'.
Make sure pointer handling code handle these modified keys gracefully
and doesn't trigger a key event and a vibration for the removed key.
|
|
|
|
1ff8526 added a bug for layouts that weren't 10 units wide.
|
|
Avoid divergences when the bottom row is modified.
|
|
Add a new boolean parameter "edgekeys" for defining keys that have the
additional (swipe) keys on the edges (top, right, left, bottom) instead
of at the corners (top left, top right, bottom left, bottom right).
|
|
When IME_FLAG_NO_ENTER_ACTION is set.
|
|
It is placed on the top-right of the enter key on every layouts.
It sends a special event (performEditorAction) instead of writing a
newline.
The "actionId" is passed through the EditorInfo object in an obfuscated
way so it's not clear whether it's using the right one.
|
|
Use xmllint.
Re-indent Java files using spaces.
|
|
|
|
KeyValue defines an ADT and some of its values, it now contains public
final fields and no internal logic.
KeyModifier handles modifiers and accents and creates new instances of
KeyValue when needed.
This operation is now properly cached.
|
|
Android has a new way of switching between input methods and this key
need to be hidden in most cases.
|
|
Remove the constant of keys per rows. Add the 'shift' attribute to
declare eventual alignment/blanks in layouts.
|
|
It was a pain to use. It was also a pain to write this though.
|
|
These keys are not useful at all in English. A new option allows to hide
them, [false] by default.
|
|
|
|
|
|
|
