Unable to long press for repeated input

[notorangee]

Hello, I'm not sure if I broke something, I can't long press and enter any key repeatedly after installation, wvkbd only outputs one character after I try to long press. I use it on surface go2 and surface pro6 , the same fault, the strange thing is that when I connect the mouse, I can long press and repeat key input, thanks for any help 🙏

[notorangee]

Note that as long as the contact range of your finger and the screen is small enough and you do not press, you only need to have one point of contact with the screen and do not move, you can get intermittent repeated input, but as long as the contact range is too large, the repeated key input will stop immediately. what happened? Is this related to iptsd multi-touch?

[notorangee]

I found out why you can't long press to repeat input. For those who come later, you just need to change the configuration option #PositionThresholdMin in IPTSD to a larger parameter, so that IPTSD will not think you are moving your finger and interrupt the long press and repeat input of wvkbd. For reference, I set it to 0.3 and it worked perfectly.

[petm5]

I think this needs to be reopened, since setting PositionThresholdMin to a high number in iptsd (in turn drastically lowering the touchscreen precision) seems to be a very hacky workaround, not to mention this setting possibly not existing on other touchscreen drivers. This seems like a problem in wvkbd itself. Maybe wvkbd needs something like a deadzone to detect movement on touchscreens. Other keyboards like squeekboard seem to register a key press as long as the touch point is above the key, but idk if that would interfere with swipe typing.

[yusi1]

I have the same issue on an Galaxy A5 (SM-A500FU), no idea how to fix it.

[proycon]

I think this needs to be reopened, since setting PositionThresholdMin to a high number in iptsd (in turn drastically lowering the touchscreen precision) seems to be a very hacky workaround, not to mention this setting possibly not existing on other touchscreen drivers. This seems like a problem in wvkbd itself. Maybe wvkbd needs something like a deadzone to detect movement on touchscreens. Other keyboards like squeekboard seem to register a key press as long as the touch point is above the key, but idk if that would interfere with swipe typing.

A deadzone sounds like an acceptable solution if this is indeed a problem that often occurs. I reopened this issue.

[icejix]

@proycon
It is, indeed. In fact, I'd say that a deadzone is very necessary. Often when I attempt to use key repeat, and move my finger even a small amount on the key, it causes it to be unpressed, decreasing reliability. I may (hackily) edit the source code of my copy in order to fix this, if it is not patched by any contributors of this project.