Microsoft Technology Licensing, LLC

Microsoft Corporation

Zhigu Holdings Limited

Todd A Torset

Reed L Townsend

Xiao Tu

Bryan Douglas Scott

Robert L Chambers

Steve Dodge

Jennifer A Teed

Samir Shiraz Pradhan

Alexander G Gounares

Rudolph Balaz

Manoj Kumar Biswas

Arin J Goldberg

Kyril Feldman

Shiraz M Somji

Kenneth W Sykes

Timothy H Kannapel

Stephen Alan Fisher

Bodin Dresevic

Adrian James Garside

Erik Michael Geidl

Subha Bhattacharyay

Brigette Krantz

Takanobu Murayama

Thomas R Wick

Gregory Nicholas Hullender

Andrew L Silverman

Tobiasz Alexander Zielinski

Jerome J Turner

Tobias Zielinski

Leroy B Keely

Jan-Kristian Markiewicz

David Andrew Matthews

Sam J George

Olumuyiwa M Durojaiye

Josh A Clow

Uros Batricevic

Krishnan Menon

Joyce Wu

Stefan Wick

Pamela De La Torre Baltierra

Mariel Young

Vipul Aneja

Steven P Dodge

Alexander J Kolmykov-Zotov

Joseph Stork Smith

Brian Ewanchuk

Todd M Landstad

Koji Kato

Stephen V Dennis

Shawn A Van Ness

Vladimir V Smirnov

Jesse Bishop

Richard Kane Sailor

Eugene A Tsimberg

Wayne Zeng

Kevin Welton

Richmond Lough

Chandramouli Kompella

Hongan Wang

Michael Russell

Tu Xiao

Embodiments relate to a computing device having storage, a processor, a display, a first human input device, and a second human input device, where the first human input device is in a first category of human input devices and the second human input device is in a second category of human input devices. The computing device may perform a process involving executing a windowing environment that manages windows of applications executing on the computing device. The windowing environment may receive raw inputs from the first and second human input devices and in turn generate input pointers for the raw inputs, respectively. The input pointers may be or include instances of an input pointer class implemented by the windowing environment, the pointer class used by the windowing environment for arbitrary different types of human input pointer devices including the first human input device and the second human input device.

Pointer unification

The inertia system provides a common platform and application-programming interface (API) for applications to extend the input received from various multi-touch hardware devices to simulate real-world behavior of application objects. To move naturally, application objects should exhibit physical characteristics such as elasticity and deceleration. When a user lifts all contacts from an object, the inertia system provides additional manipulation events to the application so that the application can handle the events as if the user was still moving the object with touch. The inertia system generates the events based on a simulation of the behavior of the objects. If the user moves an object into another object, the inertia system simulates the boundary characteristics of the objects. Thus, the inertia system provides more realistic movement for application objects manipulated using multi-touch hardware and the API provides a consistent feel to manipulations across applications.

Multi-touch object inertia simulation

The manipulation system described herein provides a common platform and application-programming interface (API) for applications to communicate with various multi-touch hardware devices, and facilitates the interpretation of multi-touch input as one or more manipulations. Manipulations map more directly to user intentions than do individual touch inputs and add support for basic transformation of objects using multiple touch contacts. An application can use manipulations to support rotating, resizing, and translating multiple objects at the same time. The manipulation system outputs two-dimensional (2D) affine transforms that contain rotation, scale, and translation information. Thus, using the manipulation system the application author can focus more on building touch-capable applications and let the manipulation system handle the underlying transformations and communication with the multi-touch hardware.

Multi-touch manipulation of application objects

An object is associated with one or more controls in a software application. An object associated with a control determines the operation of the data entry user interface when the data entry user interface is being employed to enter data into the control. More particularly, the object may communicate interface e characteristics to a component that is responsible for providing the user interface to the user. Such a component may be, for example, a shared software module that renders the user interface on a display, receives input data from the user through the user interface, and routes the entered data to a designated destination. Alternately, the object itself may create a user interface having the specified characteristics.

Utility object for specialized data entry

Computer-readable media, computerized methods, and computer systems for intuitively invoking a panning action (e.g., moving content within a content region of a display area) by applying a user-initiated input at the content region rendered at a touchscreen interface are provided. Initially, aspects of the user-initiated input include a location of actuation (e.g., touch point on the touchscreen interface) and a gesture. Upon ascertaining that the actuation location occurred within the content region and that the gesture is a drag operation, based on a distance of uninterrupted tactile contact with the touchscreen interface, a panning mode may be initiated. When in the panning mode, and if the application rendering the content at the display area supports scrolling functionality, the gesture will control movement of the content within the content region. In particular, the drag operation of the gesture will pan the content within the display area when surfaced at the touchscreen interface.

Panning content utilizing a drag operation

This document describes tools having or interacting with a touch-sensitive device with one or more contact detectors that detect a tactile input from a user making contact with the contact detectors and an input/output module that persistently identifies contact data representing the detected tactile input. This identification is unique, thereby differentiating one or more tactile inputs from other current tactile inputs represented in the contact data. Using this unique identification, the input/output module can initiate an application to provide a function, such as data entry or a mapped function, associated with the detected tactile input. These data or mapped functions may, in many instances, provide a greater depth or breadth of functions by which users may interact with applications and computer systems.

Multi-touch input platform

A multi-touch plug-in system is described herein that exposes multi-touch data for web application developers to consume in a platform independent way. The multi-touch plug-in system receives platform-specific touch data from an operating system or touch hardware, interprets the platform-specific touch data to convert the platform-specific touch data to generic touch data, and provides the generic touch data to a hosted application running within a plug-in sandbox. Often, sandboxed environments only allow identified, trusted plug-ins to execute. By managing multi-touch data within a trusted plug-in, the plug-in can ensure that hosted applications are properly restricted to well-defined behavior, while still allowing rich features such as multi-touch interaction. Thus, the multi-touch plug-in system brings rich multi-touch interaction to a web browsing environment.

Touch input for hosted applications

Growing community of inventors

Redmond, WA, United States of America

Todd A Torset