Windows 10: desktop touch issue RRS feed

  • Question

  • Hi

    We are currently testing our applications on Windows 10 preview builds. We discovered a problem with Windows desktop applications when it comes to touch. The problem occurs in both AIR applications as Unity applications for the desktop. We have also seen it happen in third party software that also uses multi touch on the desktop.

    When executing a certain order of touches (see below), touch points get stuck in the ‘touch move’ state. The most likely reason is that the ‘touch up’ events are not registered. But it might as well be an issue in the IDs of the touch points.

     To create the issue, the following actions are performed: Touch with finger 1. Keep this finger on the screen. Touch with a number of other fingers. Keep these on the screen. Release finger 1. Touch again with finger 1. From this moment, the touch points connected to the other fingers will be stuck in the ‘touch move’ state. Here are 2 movies to show the above action.
    AIR: https://youtu.be/A0ayJlq-rxQ
    Unity: https://youtu.be/Fh14DDaCTKY

    Is this issue already known at Microsoft?
    Are there other people experiencing this issue?
    Is there a workaround?

    Additional info:
    The problem only happens on Windows 10. Lower Windows versions don’t have this issue.
    Windows 8 Store App builds of our Unity games don’t have the issue. It is clearly related to desktop applications. We need desktop applications as our games are started from third party software.
    A simple WPF multi touch test application (for desktop) does NOT have the problem

    Jens Wouters
    Developer at Omnivsion Studios

    • Changed type Omnivision Studios Friday, July 10, 2015 8:42 AM The problem has been fixed and want to indicate this
    Monday, May 11, 2015 2:34 PM


  • We are happy to report the touch issue for the desktop in Windows 10 has been fixed.

    We tested on Windows 10 Home Insider Preview Build 10163 and the issue doesn't occur anymore.
    Friday, July 10, 2015 8:40 AM

All replies

  • Some further investigations:

    Game 1 (third party software)
    The Windows 10 touch issue can be seen in the tutorial part accessible in the menu.
    The next and previous buttons at the bottom, have a ‘pressed down’ state. If you execute our specific touch order using these 2 buttons, you will see the button that received the 2nd touch, will visually get locked into the ‘pressed down’ state. Thus indicating it did not receive the touch up event. But the button still functions.

    Game 2 (third party software)
    When 2 players slide the limited view (‘virtual looking glass’) over the pieces and do our specific touch order, the next time you will try to move the limited view that was touched last, will not move. After releasing this a 2nd time, you will be able again to move the limited view.

    WPF touch
    Using the tutorial which can be find online by Microsoft, we created a small test app. This WPF application does not experience the issue, but looking at the code, the way touch is handled is very different from ‘more traditional’ touch handling. They use Manipulation events.

    Halli Clack! Windows Store App
    The problems that existed in Halli Clack! for the desktop, were non-existent in our Windows Store App version. Technically, there is not that much of a difference. We use the same tech to handle touch events. Further indicating touch is being processed differently for Windows 10 desktop and Windows Store Apps.

    Windows Store Apps (Metro Apps)
    Windows Store App don’t experience the issue.

    Visual indicator difference Windows 10 desktop
    If the touch settings are all enabled for the Windows 10 desktop, you will see a black square appear in certain situations. 
    On the desktop itself, this functionality is used to simulate a right mouse click. The square will grow in size when it appears. This is shown after holding the first finger for a short time.
    Holding the first finger in our apps does not fire the right mouse square.
    But we see in our AIR applications a black square appear when we do the following: Touch with 1 finger. Keep it on the screen. Touch with a second one. Once the second touches the screen, a black square which shrinks will be visible underneath the first finger.
    Running the simple WPF touch app we have built, this black square does not show at all.
    Windows Store Apps also don’t show this black square.
    These visuals can be turned off and might not be part of the problem. But they do prove certain applications are handled differently within Windows.

    Third party app
    This third party software uses multi touch on desktop computers. This program has the same problem and it can easily be seen because the touch point indicators don’t disappear after releasing. What does happen in this software, the touch point indicators are released again once more touch points are being used. But this means if you do our specific touch order with 10 fingers, only the amount of touch points you will use (say 4) will be released from their ‘touch move’ state. The remaining touch points will still be in their ‘touch move’ state.

    Adobe AIR
    Looked into how the touch IDs are handled within AIR. Touch IDs increase after each touch.

    Update: Unity 5

    I have tested Unity 5 which now supports touch on Windows desktop out of the box. It also experiences the same issue as the other technologies.

    • Edited by Omnivision Studios Tuesday, May 26, 2015 2:19 PM Small addition to the different tests
    Wednesday, May 13, 2015 2:56 PM
  • We are happy to report the touch issue for the desktop in Windows 10 has been fixed.

    We tested on Windows 10 Home Insider Preview Build 10163 and the issue doesn't occur anymore.
    Friday, July 10, 2015 8:40 AM