-
-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Disable "done" or "send" on Enter ↵ #895
Comments
Do you customize with custom layouts? If so, you can get what you want by disabling the automatic bottom row with |
Thank you so much, it took me some time to find the xml metadata as the embedded link in the document threw an error, nonetheless found the xml in res folder of the source code. It is really such a nice keyboard. Feel free to close, unless if there is a plan to make it GUI based. |
Me too; the file path is not the correct one, nor for the other files this section points to. @Julow, could you tweak the documentation?
Do you know about the web-based layout editor? It's mentioned at the start of Custom-layouts.md |
Yeah, tried it, didn't quite work on my mobile browser, but could be browser's fault. I'm fine with config based layout. |
I have several times sent a message accidentally because of the "done" or send "↵ " key being inside the enter/return key and being available as swipe option in top right corner of the button. It doesn't appear everywhere, for instance it doesn't appear when writing this github description, but it does when writing in Telegram or Firefox search bar (Go "↵ " button).
There should be an option to disable the gesture key, or there should be an option to disable any key and gesture key with some toggle. I usually customize and enable/disable keys with "Add keys to the keyboard" option, but it doesn't provide an option for this and it is limited.
Go and "↵" might not be an issue logically, but would be nice if it is gone in all situations/contexts (optional).
This is more annoying.
The text was updated successfully, but these errors were encountered: