#Multitouch test app windows

Hover and focus effects can relay which objects are interactive and also help with targeting. Hover lets users explore and learn through tooltips associated with UI elements. There is no hover state that can trigger additional visual feedback.Ī mouse, pen/stylus, and keyboard all expose a three-state model: up (off), down (on), and hover (focus). Touch uses a two-state model: the touch surface of a display device is either touched (on) or not (off). Indirect input devices do not cause occlusion. Objects might be obscured by one or more fingertips or the user's hand. The mouse and pen/stylus can reach any part of the screen while any control should be accessible by the keyboard through tab order. Some areas on the touch surface of a display device can be difficult to reach due to finger posture and the user's grip on the device. It's easier to perform a straight-line motion with the mouse or pen/stylus because the hand that controls them travels a shorter physical distance than the cursor on the screen. This is due to the curvature of hand joints and the number of joints involved in the motion. The mouse cursor, pen/stylus cursor, and keyboard focus all assist with targeting.įingertip movements are imprecise, because a straight-line motion with one or more fingers is difficult. There is no mouse cursor to assist with targeting. Mouse movements and pen/stylus strokes supply precise x-y coordinates. The shape of the contact area changes throughout the movement. The mouse and pen/stylus supply a precise x-y coordinate. The contact area of a fingertip is greater than a single x-y coordinate, which increases the chances of unintended command activations.

#Multitouch test app windows

The following table shows some of the differences between input devices that you should consider when you design touch-optimized Windows apps. Providing unique and distinctive interaction experiences for all input devices will support the widest range of capabilities and preferences, appeal to the broadest possible audience, and attract more customers to your app. They can offer speed, accuracy, and tactile feedback that touch might not. Remember that traditional input devices (such as mouse and keyboard), are familiar and appealing to many users. If necessary, use some form of indirect input mode, such as text input for keyboard interactions, or UI affordances for mouse and pen. They should be intuitive, responsive, and discoverable, and they should let users explore your app with confidence.Įnsure that app functionality is exposed consistently across every supported input device type. The element responds immediately to any touch contact within its hit test area, and reacts appropriately to any subsequent movement of the touch contacts, including removal.Ĭustom touch gestures and interactions should be designed carefully. Touch input typically involves the direct manipulation of an element on the screen. Used to complement or modify aspects of other input methods, such as smudging an ink stroke drawn with a pen.Recognized as an alternative input method, such as mouse or pen.In contrast, interacting with an element through its properties window, dialog box, or other UI affordance is considered indirect manipulation. Interpreted as a physical gesture for direct manipulation of one or more UI elements (such as panning, rotating, resizing, or moving).The input data provided by the touch sensor can be: Movement of the touch contacts (or lack thereof, based on a time threshold).The direct contact (or proximity to, if the display has proximity sensors and supports hover detection) of one or more fingers on that display.Here, we cover the basics of using touch input in a Windows app. The Windows app includes a number of different mechanisms for handling touch input, enabling you to create an immersive experience that your users can explore with confidence. The touch contacts, and their movement, are interpreted as touch gestures and manipulations to support various user interactions. Many devices have multi-touch screens that support using one or more fingers (or touch contacts) as input. Important APIs: Windows.UI.Xaml.Input, Windows.UI.Core, In the move to a touch-first UI, it is important to understand the core differences between touch, touchpad, pen/stylus, mouse, and keyboard input. Both provide advantages and disadvantages that are unique to a technology and application. However, keep in mind that a UI optimized for touch is not always superior to a traditional UI. If you use UWP controls, support for touchpad, mouse, and pen/stylus requires no additional programming, because UWP apps provide this for free. I am taking an array of RectF i.e.Design your app with the expectation that touch will be the primary input method of your users. Recently I also had to make this screen test in my app.