Editor touch input is always double-click

Development Programming & Scripting
1

UE4 is basically unusuable for me on a touch-screen laptop. It’s double-clicking for every touch in the editor. Checkboxes instantly revert themselves when touched. File menus instantly close themselves when opened. Expanded sections instantly collapse themselves, etc.

I’m running UE4 version 4.17.1 and Win10. I’ve disabled Use Mouse for Touch, but the problem persists. That seems to be for running the game, while this issue is happening in the editor itself. Please let me know if you’d like any additional information.

2

same here , please fix this

3

i hope someone add this to the issues , it not solved .

4

Still present in 4.18. When touching a button, the press event is fired.

When the button is released, we receive 3 events: release (which is expected), then press again, then release again.

This occurs in editor or packaged builds, even when “Use mouse for touch” is disabled. We currently employ several workarounds to deal with this but they are becomingly increasingly complex and will not keep us from needing to use custom UI widgets or a custom engine build.

5

do you have show mouse cursor activated?

6

That’s for playing the game. This topic is for touch input while editing in the editor.

7

Hello ,

We are using a new bug submission form. Please navigate to the link below for more information.

Link: Unreal Engine Bug Submission Form - Announcements - Epic Developer Community Forums

Make it a great day

8

4.19.1 and this is still an issue!

9

I have 4.19.2, and its an issue for me too. Anyone found an answer for this?

Edit:
Nevermind, this solved the issue for me:
“If you set ShowMouseCursor to false in Player Controller class defaults, event should fire only once.”

10

This issue is with touchscreen performance in the editor itself, not in-game and not with the player or player controller.

11

Was a bug report ever created for this?

12

There is a similar issue here that is incorrectly marked as fixed:

13

Rudy, please note that the following issue is incorrectly marked as fixed:

14

I use the following AutoHotkey script as a stop-gap fix. Please note that it’s quite an imperfect fix and takes some getting used to. It will mess with your click-dragging on one screen, and mess with your mouse-only clicks on the other. Hold down a modifier key to bypass this hotkey.

#If WinActive("ahk_class UnrealWindow") || WinActive("ahk_class Notepad++")
;==Click fix for correct screen
$LButton::
screenX0 := 0
screenY0 := 0
screenX1 := 1920
screenY1 := 1080
MouseGetPos, mousex, mousey
if (((mousex >= screenX0) && (mousex <= screenX1)) && ((mousey >= screenY0) && (mousey <= screenY1)))
	return
else
	Click
return
15

Yes, I hold down ALT under those circumstances. It’s a trade-off.

16

This is great but as you say imperfect. When selecting components do you also get the effect as if Shift key is pressed?

17

This bug is still here, in 4.21.2, when in editor, and playing game, even without “Use mouse for touch”, “show mouse” or not, still double-click…

Win Surface with Win10 build 1803

Has anyone come up with a solution?

18

4.22.3, 4.23.0 (Preview 4)

Windows 10. Touch Screen iiyama t2252msc.

The bug is still here.

  1. The entire editor interface does not work properly

  2. Found interesting features for game itself (using only blueprints):

  • Buttons - “Clicked” fires twice only on focus. Pressing the button for the first time results in a double click, next - normal. “Pressed” and “Released” - always fires twice.

  • Inside widget blueprint we can override some functions. For example, “On Touch Started”, “On Touch Ended”. Works perfect with “Image”, “Border”, etc. But does not work with “Button”. And I have a problem with widget definition under touch.

19

Expand the “Interaction” tab in the button properties. Set values for the fields “Click Method” = “Mouse Down”, “Touch Method” = “Precise Tap”, “Press Method” = “Button Press”. It solved my problem with the buttons.

But the problem with the handler InputTouch, which after the event “Released”, again comes once again “Pressed”, then “Released” will remain.