Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.