Microsoft Technology Licensing, LLC

Vincent L Ball

Joshua Baber

Mark James McNulty

Sarah Graham Williams

Steven Nabil Bathiche

Ralf Groene

Steven W Fisher

Hua Wang

Anthony Reed

Catherine N Boulanger

John G A Weiss

Yann Florian Daniel Riche

Jan-Kristian Markiewicz

Gary Rensberger

Gene Robert Obie

Scott Robert Honji

Masahiko Kaneko

Paul Millsap

Mike Franks

Robert B Hubler

Amish Patel

Ferdinand Johannes Van Engelen

Robert D Young

Adam M O'Hern

Tim Hulford

Scott Mail

Oliver F Grabes

Daniel M Sangster

Kevin John Smith

Kam Young

Hakon Strande

Marc Descamp

Mark J Mcnulty

Dennis Meinhardt

Alice Lockhart

Mark J McNutty

Scott M Mail

Paul R Millsap

A canvas (e.g., a digital page or sheet of paper) on which a user can input data is displayed on a display device of a computing device in response to the canvas being invoked. The canvas can be invoked in different manners, such as by the user activating a switch or button at an 'eraser' end of a stylus that mimics a pen/pencil configuration. The user can input any digital data such as notes, drawings, and so forth on the canvas that he or she desires. In response to the canvas being dismissed (e.g., by the user again activating a switch or button at an 'eraser' end of a stylus that mimics a pen/pencil configuration), display of the canvas ceases. The digital data input by the user is saved or otherwise processed by the computing device.

Computing device canvas invocation and dismissal

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.

Interaction models for indirect interaction devices

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.

Pressure-based interaction for indirect touch input devices

An input device is disclosed that includes keys on a first surface and a second surface of the input device. At least some of the keys are operably coupled to a matrix including a switch for each key therein. When one of the keys is pressed, the corresponding switch is activated to provide a signal indicative thereof.

Input device with multiple sets of input keys

Automatic mode determination for an input device is disclosed. Depending on conditions of the input device, the input device can transition from a first mode to a transition mode and/or a second mode.

Automatic mode determination for an input device

Methods and systems for controlling access of application programs to an adaptive input device are described herein. One exemplary computing system includes an application programming interface executable on a computing device for controlling said access to an adaptive input device having a plurality of display regions. The application programming interface is configured to receive a display request from one of the application programs to display formatted output on the composite display and is further configured to apply at least a display sharing policy based on application-specific policy settings received from the application program for defining an application-specific area including at least one of the display regions. Further, the application programming interface is configured to generate formatted output based on the application-specific policy settings, and to send the formatted output to the application-specific area for display. The application-specific policy settings include a shared display mode and an exclusive display mode.

Controlling access of application programs to an adaptive input device

A method for carrying out application-specific mapping of input device elements (for example, human input device buttons). The method includes, from an application matching program, determining, for an application program, whether a control element event (for example, a mouse button click event) needs to carry out an action that is specific to the application program, or to perform its default action. The application matching program is configured to execute independently of the application program. A computing system that is capable of carrying out the above method is also provided.

Application-specific mapping of input device elements

Animated image for a display screen

Transitional image for a display screen

User interface for a display screen

Growing community of inventors

Kirkland, WA, United States of America

Vincent L Ball