v0.1.11

[nightkr]

Layout

• Updated Arabic layout (@Ali8101)
• Added two missing letters to the French (Punctuation) layout (@Atn-D)
• Updated Polish (Rmitura) layout (@rmitura)
• Added "toggle letters" gesture
• Removed ñ from the Portuguese layout

Removals

• Removed the $1 recognizer, any remaining users will be reverted to the default recognizer

Features

• Added a new option to type digits on counterclockwise circles (mirroring the existing clockwise option)
• Upper/lower-casing now respects the layout's locale (for example: the Turkish layout now treats İ/i and I/ı as separate pairs)

Bugfixes

• Visual feedback is now always rendered if enabled, rather than showing a blank screen for hidden characters
• Fixed a crash when loading invalid values for enum ("pick one of these options") settings
• Fixed an inconsistency in how base and overlay layers treat shift states

Changes

• Moved the pointer trail option from Aesthetics to Feedback
• Dimmed visual feedback
• Increased the swipe threshold limit

What's Changed

• Update ARMessagEase.kt by @Ali8101 in Update ARMessagEase.kt #226
• add two letters of the French alphabet that were missing from FR_PUNC_MESSAGEASE by @Atn-D in add two letters of the French alphabet that were missing from FR_PUNC_MESSAGEASE #216
• Update PLRmituraMessagEase.kt layout by @rmitura in Update PLRmituraMessagEase.kt layout #245

New Contributors

• @Ali8101 made their first contribution in Update ARMessagEase.kt #226

Full Changelog: v0.1.10...v0.1.11

---

This discussion was created from the release v0.1.11.

[lverweijen]

For me the $1 worked a bit better at recognizing circles, but now it's removed. I find it more difficult to type capitals by circular motions with the default recognizer. Maybe that's my writing style. I probably tend to make my circles a bit big (leaving the square) and I don't always fully complete the motion.

But if possible I would like to request the $1 back if possible or make the other recognizer a bit more forgiving (by default).

[nightkr]

$1 is coming back for v0.2.0 (#252).