Microsoft Technology Licensing, LLC

Steven P Dodge

Reed L Townsend

Bryan Douglas Scott

Alexander J Kolmykov-Zotov

Gregory H Parks

Alexander J Zotov

Zheng Wang

Robert J Jarrett

Emily K Rimas-Ribikauskas

Olumuyiwa M Durojaiye

Leroy B Keely

Andrew John Fuller

Xiao Tu

Manoj Kumar Biswas

Philip Ti-Fei Su

Michael C Miller

Todd M Landstad

Stefan Wick

David Andrew Matthews

Richard Jennings Duncan

David B Perry

Sumit Mehrotra

Matt Lerner

Thomas H Alphin

Chris Devaraj

Vijayakumar Rangasamy

Rudolph Balaz

Doron J Holan

Gavin M Gear

Brigette Krantz

Todd A Torset

Kyril Feldman

Sam J George

Shiraz M Somji

Timothy H Kannapel

Xu Chen

Michael H Tsang

Brian Ewanchuk

Koji Kato

Shawn A Van Ness

Stephen Alan Fisher

Eliyas Yakub

Vladimir V Smirnov

Wayne Zeng

Kevin Welton

Richmond Lough

Chandramouli Kompella

Hongan Wang

Michael Russell

Alexander J Kolmkov-Zotov

David A Perry

Townsend Reed

A service may be provided that reads sensors, and that communicates information based on the sensor readings to applications. In one example, an operating system provides a sensor interface that allows programs that run on a machine to read the values of sensors (such as an accelerometer, light meter, etc.). A service may use the interface to read the value of sensors, and may receive subscriptions to sensor values from other programs. The service may then generate messages that contain the sensor value, and may provide these messages to programs that have subscribed to the messages. The messages may contain raw sensor data. Or, the messages may contain information that is derived from the sensor data and/or from other data.

Message communication of sensor and other data

Methods of controlling the display and use of a UI element are disclosed. In an embodiment, the UI element may configured so that it initially maintains a topmost position but eventually allows other applications to assume the topmost position. In an embodiment, the display of the element may be adjusted in response to an input so that the UI element is not visible on the display. In an embodiment, the use of the UI element may allow for seamless dragging of the UI element even if the user inadvertently fails to make consistent contact with the touch-sensitive display while dragging the UI element.

Assisting user interface element use

A method for rejecting an unintentional palm touch is disclosed. In at least some embodiments, a touch is detected by a touch-sensitive surface associated with a display. Characteristics of the touch may be used to generate a set of parameters related to the touch. In an embodiment, firmware is used to determine a reliability value for the touch. The reliability value and the location of the touch is provided to a software module. The software module uses the reliability value and an activity context to determine a confidence level of the touch. In an embodiment, the confidence level may include an evaluation of changes in the reliability value over time. If the confidence level for the touch is too low, it may be rejected.

Unintentional touch rejection

Devices, methods, and computer-readable media process to distinguish user input device gestures, such as gestures input via a pen in a pen-based computing system, e.g., to quickly and reliably distinguish between electronic ink entry, single taps, double taps, press-and-hold actions, dragging operations, and the like. The devices, methods, and computer-readable media process quickly and reliably distinguishes between input device gestures by utilizing a gesture profile that includes a preferential input type, e.g. to preferentially recognize a received input as a first input type over a second input type.

Processing for distinguishing pen gestures and dynamic self-calibration of pen-based computing systems

A tablet PC having an interactive display, which is touchscreen enabled, may be enhanced to provide a user with superior usability and efficiency. A touchscreen device may be configured to receive multiple concurrent touchscreen contacts. The attributes of the multiple concurrent touchscreen contracts may be mapped to operations performed on the computing device. As a result, a user can trigger the execution of the toggle accessibility aid operation and the screen rotation operation with greater convenience. Moreover, the tablet PC may be configured to map an operation to a hand gesture or input.

Multi-touch uses, gestures, and implementation

In one or more embodiments, a bus driver, included on a local computing system, enables detection of hardware available on a host computing system for a remote access session. Upon detecting a hardware device on the host computing system, an operating system included in the local computing system may obtain a device driver for controlling data captured from the hardware device. The device driver may be used to inject data captured from the hardware device into the local operating system's input stack. In some examples, the data is injected into the local operating system's input stack at a layer that corresponds to a layer at which the data was captured on the host computing system.

Remote inking

Growing community of inventors

Sammamish, WA, United States of America

Steven P Dodge