Abstract: To allow a computer platform to provide a consistent interface for applications to use information from multi-point indirect touch input devices, an application programming interface is provided to a software interface layer that manages interaction of the system with a variety of instantiations of multi-pointer indirect touch input devices. A runtime module provides information from the indirect touch input devices to an input stack accessible by applications on the computer system. The runtime module provides mapping of contacts on the indirect touch input devices to a display.

Abstract: An indirect interaction input device, such as but not limited to a touch sensor, can provide multiple points of input, such as two or more positions in a coordinate space where a user is touching the sensor. These multiple points are in turn mapped to multiple positions on an output device such as a display. The mapping can be relative or absolute. With a relative mapping, boundary conditions for single and multiple displays are applied and, if appropriate, remedial offsets are added to the input points to maintain a desired user interaction model.

Abstract: To allow a computer platform to provide a consistent interface for applications to use information from multi-point indirect touch input devices, an application programming interface is provided to a software interface layer that manages interaction of the system with a variety of instantiations of multi-pointer indirect touch input devices. A runtime module provides information from the indirect touch input devices to an input stack accessible by applications on the computer system. The runtime module provides mapping of contacts on the indirect touch input devices to a display.

Abstract: To allow a computer platform to provide a consistent interface for applications to use information from multi-point indirect touch input devices, an application programming interface is provided to a software interface layer that manages interaction of the system with a variety of instantiations of multi-pointer indirect touch input devices.

Abstract: One or more techniques and/or systems are provided for utilizing input data received from an indirect interaction device (e.g., mouse, touchpad, etc.) as if the data was received from a direct interaction device (e.g., touchscreen). Interaction models are described for handling input data received from an indirect interaction device. For example, the interaction models may provide for the presentation of two or more targets (e.g., cursors) on a display when two or more contacts (e.g., fingers) are detected by indirect interaction device. Moreover, based upon a number of contacts detected and/or a pressured applied by respective contacts, the presented target(s) may be respectively transitioned between a hover visualization and an engage visualization. Targets in an engage visualization may manipulate a size of an object presented in a user interface, pan the object, drag the object, rotate the object, and/or otherwise engage the object, for example.

Abstract: An indirect interaction input device, such as but not limited to a touch sensor, can provide multiple points of input. These multiple points are in turn mapped to multiple positions on an output device such as a display. The multiple points of input, however, make the application of pointer ballistics and resolution differences between the input sensor and target display more difficult to manage. Thus, a characteristic of the set of points is identified and used to adjust the mapping of each of the points. For example, one way to solve this problem is to identify the input point with the least displacement from a prior frame, whether from its prior point or from a reference point. This displacement is used to adjust the mapping of the set of input points from the input device to their corresponding display coordinates.

Abstract: In an indirect interaction input device, z-information can be considered in defining a user interaction model for the device. Any measurement of displacement in a z-direction can be used, if such information is available from the input device. The pressure data can be used to define states of interaction, with transitions between these states determined by various thresholds. The device can provide raw or normalized data, and can provide state information or data defining its thresholds that specify state transitions. This information can be provided as an attribute of a contact point provided by the device. Data can be normalized across various similar devices. Applications can use the raw pressure data from the device for their own purposes, or rely on the device itself or host operating system software to interpret the pressure data according to thresholds and states.

Abstract: To allow a computer platform to provide a consistent interface for applications to use information from multi-point indirect touch input devices, an application programming interface is provided to a software interface layer that manages interaction of the system with a variety of instantiations of multi-pointer indirect touch input devices.

Abstract: One or more techniques and/or systems are provided for utilizing input data received from an indirect interaction device (e.g., mouse, touchpad, etc.) as if the data was received from a direct interaction device (e.g., touchscreen). Interaction models are described for handling input data received from an indirect interaction device. For example, the interaction models may provide for the presentation of two or more targets (e.g., cursors) on a display when two or more contacts (e.g., fingers) are detected by indirect interaction device. Moreover, based upon a number of contacts detected and/or a pressured applied by respective contacts, the presented target(s) may be respectively transitioned between a hover visualization and an engage visualization. Targets in an engage visualization may manipulate a size of an object presented in a user interface, pan the object, drag the object, rotate the object, and/or otherwise engage the object, for example.

Abstract: An indirect interaction input device, such as but not limited to a touch sensor, can provide multiple points of input. These multiple points are in turn mapped to multiple positions on an output device such as a display. The multiple points of input, however, make the application of pointer ballistics and resolution differences between the input sensor and target display more difficult to manage. Thus, a characteristic of the set of points is identified and used to adjust the mapping of each of the points. For example, one way to solve this problem is to identify the input point with the least displacement from a prior frame, whether from its prior point or from a reference point. This displacement is used to adjust the mapping of the set of input points from the input device to their corresponding display coordinates.

Abstract: An indirect interaction input device, such as but not limited to a touch sensor, can provide multiple points of input, such as two or more positions in a coordinate space where a user is touching the sensor. These multiple points are in turn mapped to multiple positions on an output device such as a display. The mapping can be relative or absolute. With a relative mapping, boundary conditions for single and multiple displays are applied and, if appropriate, remedial offsets are added to the input points to maintain a desired user interaction model.

Abstract: In an indirect interaction input device, z-information can be considered in defining a user interaction model for the device. Any measurement of displacement in a z-direction can be used, if such information is available from the input device. The pressure data can be used to define states of interaction, with transitions between these states determined by various thresholds. The device can provide raw or normalized data, and can provide state information or data defining its thresholds that specify state transitions. This information can be provided as an attribute of a contact point provided by the device. Data can be normalized across various similar devices. Applications can use the raw pressure data from the device for their own purposes, or rely on the device itself or host operating system software to interpret the pressure data according to thresholds and states.