You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve noticed that when using touchscreen layouts with longpress keys that I can also access the longpress character by flicking up/north. From I can tell this defaults to the last longpress character if there’s more than one. This happens without needing to add an explicit flick gesture.
Question:
I find this really useful where there is one longpress character. It allows for more fluent input. I’d therefore like to include this behaviour in the instructions for my keyboard layouts. However, I can’t find any reference to it in the Keyman documentation (sorry if I’ve missed it).
Could I check, is this intentional behaviour? Am I safe to describe it as a feature of my layouts with longpress keys?
Should the behavior be changed or the document? Please let me know if this is the intended behavior. Thank you!
Reproduce the bug
Open Keyman for iPhone and iPad
Install and select EuroLatin Keyboard
Up-flick a key which has both long press and flick keys.
Meng-Heng
changed the title
bug(ios): up-flick gesture opens the long press keys submenu
bug(ios): up-flick gesture opens the long press keys submenu when no up-flick key is assigned
Jan 15, 2025
Describe the bug
Source of report: https://community.software.sil.org/t/do-longpress-keys-include-a-flick-gesture-automatically/9658
Question:
Should the behavior be changed or the document? Please let me know if this is the intended behavior. Thank you!
Reproduce the bug
Expected behavior
Please refer to the description above.
Related issues
No response
Keyman apps
Keyman version
17.0 & 18.0.164-alpha
Operating system
iOS
Device
iPhone 11 Pro Max (18.0.164-alpha)
Target application
No response
Browser
No response
Keyboard name
EuroLatin
Keyboard version
3.0.3
Language name
English
Additional context
Link to keyboard: EuroLatin (SIL) keyboard
The text was updated successfully, but these errors were encountered: