Microsoft Technology Licensing, LLC

Pravin Kumar Santiago

Craig Steven Ranta

Weidong Zhao

Aleksandar Uzelac

Stephen Harry Wright

Jeremy De Souza

David Alan Stevens

Takahiro Shigemitsu

John Graham Pierce

Briggs A Willoughby

Timothy Allen Wright

Stanimir Naskov Kirilov

Jeffrey C Maier

Robert T Perry

Thomas W Olsen

Andrey Borissov Batchvarov

Reiner Fink

Masahiko Kaneko

Mohamed Sadek

Raju Ramanathan

Alice Tang

Nikola Letié

Ruoyang Li

Alice M Tang

A computer configured to selectively use prediction to compensate for a latency of an input device. The input device may be a touch screen. Processing of touch inputs may lead to a latency between the user performing a touch input and the touch screen display responding to the touch input. A touch screen component predicts a subsequent position of a touch contact point based on the sensed positions of the touch contact point. The component may be a software component that provides a predictive output that can be selectively used based on a characteristic of a touch input. The component may be generic such that it may be applied on multiple types of computers equipped with different types of touch sensing hardware configured with any suitable settings. The component's output may be used to control the touch screen display.

Predictive compensation for a latency of an input device

Touchscreen testing techniques are described. In one or more implementations, a piece of conductor (e.g., metal) is positioned as proximal to a touchscreen device and the touchscreen device is tested by simulating a touch of a user. This technique may be utilized to perform a variety of different testing of a touchscreen device, such as to test latency and probabilistic latency. Additional techniques are also described including contact geometry testing techniques.

Contact geometry tests

Techniques for an input object for routing input for visual elements are described. In at least some embodiments, a region of a display area includes multiple graphic elements that can be generated and/or managed by different graphics functionalities. For instance, a graphical user interface (GUI) for an application can include a primary window and visual elements within the primary window, such as banners, control buttons, menus, Tillable fields, and so forth. In at least some embodiments, the primary window of the GUI can be managed by a first graphics functionality, while one or more visual elements within the primary window can be managed by a second graphics functionality. In accordance with one or more embodiments, an input object is employed to route input to visual elements to a graphics functionality responsible for managing the visual elements.

Input object for routing input for visual elements

Probabilistic latency modeling

Latency measurement

An application may be provided with an interface for hiding a cursor from or showing a cursor to a video driver and for causing cursor information to be saved in data storage and retrieved from data storage. The interface may include an application program interface (API), which may be callable from the application program. The interface may also include one or more bits included in a video driver, such that the modification of any of the one or more bits may change operation of the video driver. Modification of at least some of the bits may cause a cursor to be hidden from the video driver, may cause a previously hidden cursor to be shown to the video driver, may cause cursor information to be saved in a data storage, or may cause the cursor information to be retrieved from the data storage.

Selective display of cursor

Described is the selective exclusion of content returned in a requested screen capture operation, wherein exclusion may be determined by a window category and the requesting application program. For example, a magnification program will not received content captured from its own layered window or from any other layered magnification windows. A registration mechanism obtains and maintains a window handle for any window registered for exclusion. A screen capture mechanism uses the information to determine whether to exclude the content of windows when returning the captured screen content. Exclusion may be accomplished by enumerating areas that are not covered by any layered window and copying those areas to a screen representation buffer or the like, and separately enumerating areas that are covered by at least one layered window. A covered area is only copied to the screen representation when it does not correspond to an excluded window.

Selective window exclusion for captured content

Described is a filtering mechanism/process that selectively controls whether graphics primitives are provided to a given driver. For example, graphics primitives of an accessibility (e.g., magnification) program may be excluded from being obtained by mirror drivers associated with the accessibility programs, so that the mirror drivers receive only the primitives of unmagnified windows. A registration mechanism allows a program to identify its window as being associated with a class of drivers for filtering, and the drivers may identify themselves as being of the class. By maintaining data that associates windows with a class of drivers, when graphics primitives associated with a registered window are received, a filtering operation be activated to determine which graphics primitives are provided to which driver or drivers. Filtering may be by exclusion to prevent certain primitives from being obtained by excluded drivers, or by inclusion whereby only included drivers receive certain primitives.

Selective rendering for driver classes

Described is a technology including a mechanism that when activated, detects a call to a device independent bitmap. An appropriate mirror driver, such as one or more registered as an accessibility driver, may then be notified of the call. The mechanism may be activated upon creation or selection of the device independent bitmap, and may comprise a wrapper/driver that, from the perspective of the mirror driver, simulates a call to a device dependent bitmap. The notification may be performed by having the driver communicate a function call that emulates a drawing primitive to the mirror driver.

Mirror driver notification of device independent bitmap drawing calls

Growing community of inventors

Issaquah, WA, United States of America

Pravin Kumar Santiago