| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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.
|
|
Each layouts can chose which key are localized instead of specifying it
globally for each key.
Important keys are no longer removed from layouts if the 'extra_keys'
mechanism is not working properly. This can happen if language tags
specified in method.xml don't match the user's language.
Removed some currency symbols from some layouts. They are all in the Fn
layer.
|
|
The previous limit was checking d-1 and d+1, the new limit also tries
d-2 and d+2.
|
|
Fix the bug introduced in the parent commit.
|
|
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
|
|
Since SDK 21, applications can set the background color of the
navigation bar. This is normally simply an item in a theme but it is
more complicated for keyboards.
|
|
|
|
It was possible to latch and lock the same modifier several time at the
same time independently. Remove that.
|
|
This is unexpected but happened to a user. Perhaps because the OS
returned bogus or fake results in imm.getEnabledInputMethodList ?
|
|
When typing fast, a second key might be pressed before the first is
released.
Clearing modifiers earlier would prevent this but would break modifiers
placed in corners (especially the accent keys). Instead, don't take
latched modifiers into account when registering the second press.
A new flag is needed to not interfere with holding modifers, which is
merged with the norepeat flag.
|
|
The View no longer keeps flags for something other than rendering.
|
|
The required version of fontforge (from 2020!) is not available in many
distros. This is an annoying for contributors and greatly complicated
the CI and F-Droid scripts.
The generated font file is now included in the sources. Fontforge is
still needed when adding new glyphs but this is not a common operation.
|
|
* Added neo 2 layout
* Move accents away from screen edge into second row
|
|
Will be used by the Hungarian language.
|
|
|
|
Requires two new diacritics: ogonek and dot_above.
The new accents are also added to the Latvian layout as the two language
can be close but not to the other localized layouts. A new mechanism is
needed to reproducibly add extra keys to layouts without manual
placement.
|
|
Android 6 uses Java 1.7, the only incompatible feature in use was
lambdas.
|
|
The Korean layout id was not consistent and this caused a crash.
|
|
Resources.getFloat is new from API 29.
|
|
Allow specifying a layout for programming and add a key for switching to
it easily.
The switching key is placed on the top edge of the space bar.
The option has no effect by default because the ergonomic isn't ideal,
it needs to be enabled explicitly.
Users of Latin-script languages certainly prefer to use one layout (for
programming or not). This feature might be removed in favor of a better
language-switching mechanisms in the future.
|
|
The symbol isn't clear enough.
|
|
The switch_numeric key is generally more important, especially in the
numeric pane.
|
|
Revert to previous version, the original google material icon,
which is not rounded, and it looks better with the rest of the keyboard,
also more correct to represent the open box unicode space char,
instead of a smile
|
|
Fn+e = €
Fn+l = £
Fn+r = ₹
Fn+y = ¥
Fn+c = ¢
Fn+p = ₱
|
|
* Add `Arrows` and `Box` accent system
|
|
* Add Korean layout
|
|
The previous computation was very different depending on the device's
screen and accessibility options.
Given that the keyboard is supposed to fill all the space in one
dimension, the dpi unit makes little sense.
The formula doesn't mean anything in particular, it takes into account
both dimensions (x and y) and should be close to the dpi in the
diagonals (which is the direction of swipe).
This changes the actual value, on a 1920x1080 480dpi screen, the value
is increased by 20%.
|
|
|
|
Add simple arrows to the numeric keypad. Using the Fn key with these arrows will
output double arrows.
|
|
|
|
Also removed almost all combinations of diacritics and symbols to create extra
symbols.
|
|
Tab is from IcoMoon. Backspace and Delete are from materialdesignicons.
|
|
The accents are taken from the Roboto Regular font (Apache 2.0), added
the dotted circle and exported with FontForge.
The argument to FontForge's Import function are changed, the fifth
argument controls the accuracy and needed to be lowered otherwise the
grave accent wouldn't be rendered at all.
|
|
Revert them to previous version, but now using SVG icons
instead of a ttf font file
|
|
When changing any numeric setting and cancelling this change, the change would not
be persisted, but the summary in the setting screen would show the last position
of the slider instead of the correct unchanged value.
This commit fixes this on the most simple way by resetting the slider position to
the persisted value.
|
|
These keys are shown only when Fn is activated, "placeholder" keys are
placed in the layouts.
|
|
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.
|
|
The "dotted circle" character combined with the accent was badly
rendered on many devices.
|
|
Recover the provenance of each glyphs and remove the base_font.ttf file.
|
|
Keep the glyphs in SVG format and build the font using a FontForge
script.
A part of the previous font is kept because the sources is lost.
This adds a new dependency to the build system, fontforge.
|
|
On some devices, bogus touch events can be sent while holding a key.
With modulated keys, it can happens on top of other keys.
Ignore every new pointers when a modulated key is pressed.
|
|
Ensure the switching key is shown when there's several subtypes enabled,
even if Android says not to show it.
|
|
* Providing a comprehensible Brazilian Portuguese keyboard layout
removed cedille as it is already provided by an independent key;
changed layout to correspond to the locale
|
|
Handling this event is part of the API but was never done. This caused
unstoppable key-repeat.
This event isn't common, the only way I found on Android 10 is to switch
to the emoji keyboard while holding a key. Some apps might cause this
event more often.
|
|
|
|
Useful when debugging why the keyboard doesn't work as expected with a
specific app.
|
|
|
