| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Thanks to the previous commit, a modifier key can now be more complex
than just a KeyValue.Modifier. This allows a more elegant implementation
of the compose key, that could be taken as a base for other features
(eg. unicode hex entry, hangul)
The COMPOSE_PENDING modifier is removed as keys of kind Compose_pending
can act as a modifier. This has the advantage of highlighting the key
that was last pressed in the sequence.
Rules are added to Pointers: Non-special but latchable keys must clear
latches and cannot be locked with a long press. These rules were not
needed before but were intended.
|
|
Allow keys of a kind other than Modifier to be a modifier.
This requires writing a compareTo function for KeyValue. Fields are
compared in this order: Kind, value, flags, symbol.
|
|
The performance characteristics of this function will change in future
plans.
|
|
The preferred pos mechanism could cause an out of bounds access on 1 row
layouts.
|
|
|
|
|
|
The grid layout was not likeable.
|
|
|
|
|
|
'FLAG_LOCKED' and 'FLAG_FAKE_PTR' are only used within Pointers.
Define new flags in Pointers and remove these from KeyValue. Also allows
to define new flags.
|
|
|
|
|
|
|
|
|
|
It is mandatory for Google Play.
|
|
Metadata directories were renamed while adding store descriptions into
strings files for simplicity.
This interferes with releases so is released.
An hardcoded lookup table is used instead.
|
|
|
|
|
|
added shift modifier characters
Add support for gujarati numerals
Co-authored-by: yogesh-b <yogesh@improwised.com>
|
|
Shift locked via the "caps lock" key use the "fake pointer" mechanism
that is also used by auto-capitalisation.
Make sure that unlatching a fake pointer do not disabled a locked
modifier.
The implementation is moved into the Pointers class for a safer API and
easier implementation.
|
|
|
|
The original author is @sejkm in https://github.com/Julow/Unexpected-Keyboard/issues/573
|
|
There's no json file yet, this was part of an experiment.
Add a missing escape rule and detect colliding sequences.
|
|
Mention the source of the sequences files.
|
|
Add éèàç directly to the layout, which removes the corresponding dead
keys.
Remove the requirement for ù and ÿ from method.xml, which are extremely
rare and can be typed via the compose key.
|
|
|
|
The same way as the numpad is modified.
|
|
The number keys were constructed in the wrong way: the rendered symbol
was correct but not the underlying character that is typed.
|
|
Without this, the system might choose en-GB and fr-CH.
This makes them more similar to en-US and fr-FR (without € in extra keys).
|
|
|
|
Without the config key, the user risk being locked in a custom layout
that lacks an escape key like 'switch_numpad', 'change_method', etc..
|
|
Thanks to everyone considering funding the development of the app.
|
|
* Relicense layouts under CC0
Layout definitions are licensed differently from the rest of the
application source code to allow use in other projects related or
unrelated to Unexpected Keyboard.
Some layouts are not re-licensed and their original copyright continues
to apply. The copyright notice is added at the top of the files.
* Contributing: Mention layout licensing
|
|
* CI: Run 'check_layout.py'
Ensures that 'check_layout.output' is not outdated.
Also, update it.
* CI: Check new store descriptions
When a store description is added, 'python3 sync_translations.py' leaves
an untracked file that is not checked.
This makes sure that untracked store descriptions are noticed in CI.
|
|
|
|
|
|
|
|
Though it is not useful in the greek-math layout, it could give ideas
for new sequences.
|
|
Keys that are not in the pending compose sequence are greyed out with
the new 'FLAG_GREYED' flag.
|
|
Themes do not dim secondary keys the same way due to the "offset"
mechanism. Instead, use a ratio that is the same for every themes.
It's still possible to override this ratio per theme.
|
|
The kind field wasn't large enough to hold the new Compose_pending kind.
The flags field is reduced in size by removing a free spot.
The FLAGS_BITS mask is defined in a safer way.
|
|
|
|
Keys that are not part of any possible sequences are now dimmed and
still usable instead of being removed, which felt weird.
|
|
compile.py implements a parser for X11's Compose.pre files. A lot of
code is necessary to interpret character names but thanksfully, the name
of most characters is contained in the file.
The state machine is compiled into two char arrays which unfortunately
requires an expensive initialisation and allocation.
|
|
The COMPOSE_PENDING modifier indicate whether a compose sequence is in
progress. The new key of kind Compose_pending sets the current state of
the sequence.
The compose sequences are compiled into a state machine by a python
script into a compact encoding.
The state of the pending compose is determined by the index of a state.
|
|
Adapted from latn_qwerty_us
* Make it the default layout for en-GB
|
|
Removing "g" as it was used two times as a main key.
shift="0.5" added
|
|
The pin entry layout shouldn't be inverted as the letter indications
would be meaningless and the order would be opposite to what the option
specifies.
The enter and action key are swapped as the automatic swapping is also
removed.
|
|
I made more clearer how to use the keys
|
|
Among others:
- Use `apply` instead of `commit` when saving shared preferences.
- Avoid inlined Api
- Remove unused resources
|
