Skip to content
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

Prevent accidental key press when swiping the extra keys view to the left to access the text input view #905

Open
vovcacik opened this issue Nov 4, 2018 · 7 comments

Comments

@vovcacik
Copy link

commented Nov 4, 2018

The title says it all.

User needs to be careful what key to lay his finger on when swiping the extra keys view, because when the swipe begins it registers as key press. One example for all: the "ARROW_UP" button will fill in previous command, this obstructs the new command you are about to type in the text input view.

https://wiki.termux.com/wiki/Touch_Keyboard

@ticalc-travis

This comment has been minimized.

Copy link

commented Nov 22, 2018

I can confirm this issue. This seems to have only become an issue when the extra keys thing was revamped and changed to two rows. Older versions of Termux did not have this problem.

This behavior makes the input view virtually unusable because there is no way (that I can find) to swipe the extra keys without sending a spurious keypress to the terminal, thereby messing up the state I need to begin text input in the first place.

@eekee

This comment has been minimized.

Copy link

commented Dec 21, 2018

Same here, installed and upgraded today. Tolerable if swiping on CTRL, I guess.

@9001

This comment has been minimized.

Copy link

commented Jan 31, 2019

I tried adding a blank key to the extra keys bar, hoping that would be a draggable point with no side effects -- instead this crashes Termux :p

I would much prefer if sliding in from the right side of the screen toggled this, similar to the burger menu on the left, as I do not otherwise use the extra input bar at all. Adding it just for the purpose of toggling between android-native and terminal-native text input results in an unfortunate waste of space.

@Quasic

This comment has been minimized.

Copy link
Contributor

commented Feb 2, 2019

I have the same problem since the keyboard was updated to two rows.

@epitron

This comment has been minimized.

Copy link

commented Feb 8, 2019

Ditto!

Is the bar a custom GUI element? If so, a good solution would be to modify its logic so that the keys are activated on release of the button, and if the bar if swiped, the release event is blocked.

@Quasic

This comment has been minimized.

Copy link
Contributor

commented Mar 2, 2019

#1014 fixed the empty button crash

@Mhowser

This comment has been minimized.

Copy link

commented Jun 18, 2019

Any progress on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.