| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This mode is annoying to some users and is disabled in most text views.
The keyboard has a fixed sized relative to the height of the screen in
landscape mode. The keyboard can't take more space than expected,
currently.
This might cause problems in the future and might be hidden behind an
option if one is found. Every text views so far seemed to behave fine.
|
|
Broken since 31d6a70d.
|
|
|
|
* Basic greek layout.
|
|
It is unclear how _autocap.started is not called first but nothing is
preventing to initialize things earlier.
|
|
* Hindi Keyboard Layout
Hindi keyboard layout added
Basic symbols like brackets, colons etc are useful. This includes ( ) { } [ ] \ / ÷ - + = ! % : ; . , ?
|
|
In Turkish, upper case of 'iı' is 'İI' but Java's toUpperCase will
return 'II'.
To make 'İ' accessible, make it the shift of 'ı'. This has the
inconvenient of swapping i and ı on the keyboard.
|
|
For some reason, 'subtype' can be null. Perhaps because the keyboard is
started before the IMM is ready.
|
|
* Added Czech translation and layout
Translated keyboard and created Czech multilingual "practical" layout for faster typing and typing in commonly used languages (German, Slovak + French w/accents)
* Update (Rephrase) full_description.txt
... to better suit the language and naturally promote keyboard's features and possibilities to a wider audience.
|
|
- Detect when the input box is cleared
- Avoid looking up keys on the keyboard every time the shift state needs
to change.
|
|
The autocapitalisation is asking the editor about whether to enable
shift and must make sure to ask after the editor is done processing the
events.
|
|
|
|
The Fn+switch_numeric shortcut might be hard to discover or too slow for
heavy users.
A location is allocated for the key so it has a consistent placement.
|
|
Avoid dropping some keys on crowded layouts.
|
|
* Add white e-ing oriented theme
Co-authored-by: Jules Aguillon <jules@j3s.fr>
|
|
|
|
* Bangla Layout
|
|
Allows to add more keys to the keyboard from a predefined list.
The implementation doesn't use MultiSelectListPreference because it
doesn't seem possible to change the item layout to properly show the
rendered symbols.
|
|
This is unexpected but happens once.
|
|
Add a flag to recognize fake pointers and avoid clearing the
intentionally locked shift key.
|
|
Change the capitalisation algorithm to use Android's
'getCursorCapsMode'. This requires a bit of cursor calculations but
should feel more standard.
The auto completion only triggers after a space is typed or backspace is
pressed.
|
|
Modifiers can be locked with a long press. The key repeat mechanism is re-used
and the press timeout is the same.
Every modifiers can be locked that way, not only the "lockable" ones.
The previous behavior can be enabled in the settings (for shift only)
but the default is changed.
|
|
|
|
Disable capitalisation just after an arrow kind is pressed to avoid
interrupting navigation.
|
|
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.
|
|
|
|
|
|
Add a shortcut to switch to the greekmath pane directly from the main
layout.
|
|
The key is placed on the 3rd row of the numeric pane, by taking some
space from the shift key.
|
|
|
|
The Math.floorMod method was added on API level 24.
|
|
Bring back the "Vibration" option.
The duration option isn't added back because the vibration settings are
still handled by Android. In fact, the option has no effect if the
vibration are disabled in the system settings.
This partially reverts commit ef03dfed5c802a855c4655204eee39a8769cfed7.
|
|
The "f11_placeholder" and "f12_placeholder" keys were equals since
31d6a70.
Add an incrementing id into the unused key value to differentiate
placeholder values.
|
|
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.
|
|
This is no longer necessary since repeating key no longer cause a
vibration.
|
|
Instead of using the vibrator directly, use performHapticFeedback, which
will integrate better with the system settings.
|
|
Dimens weren't refreshed when the orientation changed. Dimens are not
the right solution anyway, use scaling factors instead.
|
|
Space between the keys and margin on the left and right edges of the
screen.
|
|
The previous fixed value of 55% was too high. The new default value is
50% and it is customizable.
|
|
|
|
This option cannot be implemented easily now that the set of "accents"
(localized keys) isn't defined.
|
|
This makes KeyValue objects smaller. 'equals' and 'hashCode' are now
implemented too. Key names are still used to recognise keys with special
meaning, but not for comparing keys anymore.
|
|
Since cc571ea
|
|
The class has a complicated internal logic, it is no longer reasonable
to extend it.
|
|
With a small number of flags now, it's possible to remove one more
field.
|
|
Negative values for internal events are preventing further refactoring.
Add a new kind of key and split internal events (now Event) and
Android's key events (now Keyevent).
Use enums events and modifiers outside of the KeyValue class.
Internally, they are converted to and from integer.
|
|
These two fields couldn't have an interesting value at the same time.
As we can no longer rely on a special value to distinguish between
what's the kind, the kind of the key is explicitly encoded in the two
most significative bits of the _flags field.
Extra nice thing: This removes the special values 'EVENT_NONE' and 'CHAR_NONE'.
|
|
Two advantages:
- No need to distinguish modifiers in KeyEventHandler. The KeyValue is
enough to decide what action to do.
- Keys are never a Char and Event at the same time, fields can be
merged.
|
|
The meaning of the public fields of KeyValue was quite complicated and
not handled consistently accross the app.
Make these fields private and add a more abstract API on top.
The meaning of these fields changed recently and it wasn't an easy
change. I plan on making more changes in the future.
|
|
* Turkish layout & translation
|
