Closed deadalnix closed 7 months ago
Yeah.. I guess the fix here would be to distinguish between "true" shift and capslock-shift.
Have you considered supporting dead keys? Would that be difficult considering the current codebase? I started to look into the code, but i'm not at a point yet where I have a good grasp on it.
With dead keys, we can leave the keyboard config deal with this, and I have a lot of ideas as to what can be done with them.
Le sam. 6 avr. 2024 à 00:48, Natalie Klestrup Röijezon < @.***> a écrit :
Yeah.. I guess the fix here would be to distinguish between "true" shift and capslock-shift.
— Reply to this email directly, view it on GitHub https://github.com/nightkr/flickboard/issues/141#issuecomment-2040728460, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGQQ2N3YMVZ754UMZRJXSLY34S5FAVCNFSM6AAAAABFVVXASGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBQG4ZDQNBWGA . You are receiving this because you authored the thread.Message ID: @.***>
We already support dead keys (see https://github.com/nightkr/flickboard/blob/605bef3de5da6c028789722e8981b5d4846232ea/app/src/main/java/se/nullable/flickboard/KeyboardService.kt#L195-L198), though with a postfix syntax (like ME, you type a¨
for ä
, vs ¨a
on a regular QWERTY keyboard).
Context
No response
Steps to reproduce
Expected behavior
Punctuation style character such as "?" remain unaffected.
Actual behavior
Punctuation style character such as "?" is changed in "¿". The same happen for many non letter characters.
Android version
Android 9
Device
Galaxy S8
Other details
While this may seems like a small deal, this actually makes caps lock unusable.
Acknowledgements