Search Issue Tracker

By Design

Votes

2

Found in

5.3.1p1

Issue ID

763310

Regression

No

Standalone Input Module Touch Input Functioning like Mouse Pointer

UI

-

StandaloneInputModule behaves differently to TouchInputModule on touch screen devices when processing touch input. StandaloneInputModule is more similar to an emulated mouse.

1 Make Unity project containing a UI button that has a distinct "High lighted color".
2 Set the EventSystem's input module to be a StandAloneInputModule.
3 Deploy to a touch screen device.
4 Press the button and remove finger within the button. Notice it stays high lighted.
5 Repeat the above process but using a TouchInputModule. Notice the button does not stay highlighted after removal of finger.

Comments (2)

  1. dlackey_AEgisTG

    Aug 31, 2016 18:01

    Still an issue in 5.4.0f3.

  2. Sevdanski

    Jun 03, 2016 12:37

    I have Back and Next navigation buttons that are in the same position on multiple pages. When touching the next button and changing the page, the button on the new page is automatically highlighted as if I had rolled over it.

    I have also noticed that on a scrolling list of buttons and flick the list so it has some momentum the buttons will go through a rollover state as they move under the last point I touched.

    The deprecated TouchInputModule does not suffer either of these effects. My assumption is that the StandaloneInputModule is treating the touch position as the mouse position.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.