Alan K Stephenson, 56Kent, WA

2013022, Aug 29, 2013

Feb 27, 2012

13/405737

Alan W. Stephenson - Seattle WA, US
Xiao Tu - Sammamish WA, US
Scott S. Sheehan - Redmond WA, US
Robert K. Mickle - Seattle WA, US
Changsin Lee - Redmond WA, US

MICROSOFT CORPORATION - Redmond WA

G06F 11/28

714 27, 714E11178

APIs to test a device are described. In one or more implementations, a device includes a housing, one or more sensors supported by the housing, and one or more modules disposed within the housing that are implemented at least partially in hardware. The one or more modules are configured to process inputs detected using the one or more sensors and expose one or more application programming interfaces to a robot to cause the robot to perform one or more operations that are detectable by the one or more sensors, the one or more operations usable to test detection performed by the one or more sensors and the processing of the inputs performed by the one or more modules.

2014007, Mar 13, 2014

Sep 11, 2012

13/609258

Stephen Wright - Bothell WA, US
Hirofumi Yamamoto - Bellevue WA, US
Pak Kiu Chung - Redmond WA, US
Raju Ramanathan - Redmond WA, US
Krishnan Menon - Redmond WA, US
Lawrence Osterman - Woodinville WA, US
Alan Stephenson - Redmond WA, US
Reed Townsend - Kirkland WA, US
Jacob Rossi - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 3/00

719321, 719328

In one embodiment, a unified pointer message may describe in a single type of pointer message a coordinate input from a user via multiple types of pointer devices. An input device interface may receive a coordinate input from an input device. A processor may execute an application programming interface layer that creates a unified pointer message for the coordinate input . The processor may send the unified pointer message to an application. The processor may process a device specific data set unhandled by the application.

2014037, Dec 18, 2014

Jun 17, 2013

13/919143

- Redmond WA, US
David Abzarian - Kenmore WA, US
Silvano Bonacina - Redmond WA, US
Changsin Lee - Redmond WA, US
Alan W. Stephenson - Redmond WA, US
Michael A. Nelte - Redmond WA, US
Uros Batricevic - Redmond WA, US

G01B 21/04

702 94

The techniques described herein are directed to receiving parameters directed to correcting spatial error and/or jitter associated with an interaction device connected to a computing device. In some instances, the parameters are encrypted parameters that may be decrypted and consumed to correct the spatial error and/or the jitter associated with the interaction device. For instance, the parameters may provide an adjustment to one or more reported positions of input received from a detection area of the interaction device, so that a display position more accurately reflects, based on the adjustment, an actual position of input on the detection area of the interaction device.

2014037, Dec 18, 2014

Jun 14, 2013

13/918645

- Redmond WA, US
John Wesley Terrell - Kirkland WA, US
Fei Xiong - Redmond WA, US
Michael J. Ens - Redmond WA, US
Xiao Tu - Medina WA, US
Nicolas J. Brun - Seattle WA, US
Ming Huang - Bellevue WA, US
Jan-Kristian Markiewicz - Redmond WA, US
Alan William Stephenson - Redmond WA, US
Michael John Patten - Sammamish WA, US
Jon Gabriel Clapper - Seattle WA, US

G06F 3/0486
G06F 3/0488

715769

High performance touch drag and drop are described. In embodiments, a multi-threaded architecture is implemented to include at least a manipulation thread and an independent hit test thread. The manipulation thread is configured to receive one or more messages associated with an input and send data associated with the messages to the independent hit test thread. The independent hit test thread is configured to perform an independent hit test to determine whether the input hit an element that is eligible for a particular action, and identify an interaction model associated with the input. The independent hit test thread also sends an indication of the interaction model to the manipulation thread to enable the manipulation thread to detect whether the particular action is triggered.

2014031, Oct 16, 2014

Apr 15, 2013

13/863069

- Redmond WA, US
Christopher Doan - Seattle WA, US
Alan Stephenson - Bellevue WA, US
Bret Anderson - Kirkland WA, US
Michael Seibert - Redmond WA, US
Robert Jarrett - Seattle WA, US
Aleksandar Uzelac - Seattle WA, US
Steven Welch - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 3/01

715863

Systems and methods of blocking, ignoring, suspending, or otherwise altering edge-related UI gestures on touch-sensitive computing devices or on non-touch sensitive computing devices having active edge I/O commands in certain situations are disclosed. In one embodiment, a second UI gesture coming from an outside edge may be altered after a first UI gesture from a user using an running application under certain conditions—e.g., if the second UI gesture is made within a certain time period after the first UI gesture, the second UI gesture is made within a certain proximity of the first UI gesture, etc. In another embodiment, a computing device is disclosed that comprises a controller, a display screen and an operating system that alters certain edge-related UI gestures that might be made by an operating system if, e.g., certain conditions are present.