Abstract: The techniques described herein implement a classification process to evaluate information associated with a tool input (e.g., from an input tool such as a pen or a stylus) and a user touch input (e.g., from a finger or a palm of a hand) to determine whether the user touch input is an intended or an unintended touch input. The information evaluated may be associated with an arrival of the tool input relative to an arrival of the user touch input. The information evaluated may also be associated with a movement of the tool input relative to a movement of the user touch input. In various implementations, the techniques may calculate an evaluation score and compare the evaluation score to a confidence classification threshold. If a confident classification cannot be achieved, the techniques further the classification process as more information associated with the inputs is received.

Abstract: The techniques described herein implement a classification process to evaluate information associated with a tool input (e.g., from an input tool such as a pen or a stylus) and a user touch input (e.g., from a finger or a palm of a hand) to determine whether the user touch input is an intended or an unintended touch input. The information evaluated may be associated with an arrival of the tool input relative to an arrival of the user touch input. The information evaluated may also be associated with a movement of the tool input relative to a movement of the user touch input. In various implementations, the techniques may calculate an evaluation score and compare the evaluation score to a confidence classification threshold. If a confident classification cannot be achieved, the techniques further the classification process as more information associated with the inputs is received.

Abstract: The techniques described herein implement a classification process to evaluate information associated with a tool input (e.g., from an input tool such as a pen or a stylus) and a user touch input (e.g., from a finger or a palm of a hand) to determine whether the user touch input is an intended or an unintended touch input. The information evaluated may be associated with an arrival of the tool input relative to an arrival of the user touch input. The information evaluated may also be associated with a movement of the tool input relative to a movement of the user touch input. In various implementations, the techniques may calculate an evaluation score and compare the evaluation score to a confidence classification threshold. If a confident classification cannot be achieved, the techniques further the classification process as more information associated with the inputs is received.

Abstract: Techniques and architectures for detecting the handedness of a user from touch input and suppressing unintentional touch input are described. The techniques and architectures may analyze short-lived contacts that occur on a touch surface around a same time as input from an input tool to determine a hand that a user is using to hold the input tool. An inactive region may be established for the touch surface based on the hand determination and/or contextual information related to the user, the touch surface and so on. The inactive region may allow unintentional input to be identified and suppressed.

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

Abstract: Techniques and architectures for detecting the handedness of a user from touch input and suppressing unintentional touch input are described. The techniques and architectures may analyze short-lived contacts that occur on a touch surface around a same time as input from an input tool to determine a hand that a user is using to hold the input tool. An inactive region may be established for the touch surface based on the hand determination and/or contextual information related to the user, the touch surface and so on. The inactive region may allow unintentional input to be identified and suppressed.

Abstract: The techniques described herein implement a classification process to evaluate information associated with a tool input (e.g., from an input tool such as a pen or a stylus) and a user touch input (e.g., from a finger or a palm of a hand) to determine whether the user touch input is an intended or an unintended touch input. The information evaluated may be associated with an arrival of the tool input relative to an arrival of the user touch input. The information evaluated may also be associated with a movement of the tool input relative to a movement of the user touch input. In various implementations, the techniques may calculate an evaluation score and compare the evaluation score to a confidence classification threshold. If a confident classification cannot be achieved, the techniques further the classification process as more information associated with the inputs is received.

Abstract: The techniques described herein implement a classification process to evaluate information associated with a tool input (e.g., from an input tool such as a pen or a stylus) and a user touch input (e.g., from a finger or a palm of a hand) to determine whether the user touch input is an intended or an unintended touch input. The information evaluated may be associated with an arrival of the tool input relative to an arrival of the user touch input. The information evaluated may also be associated with a movement of the tool input relative to a movement of the user touch input. In various implementations, the techniques may calculate an evaluation score and compare the evaluation score to a confidence classification threshold. If a confident classification cannot be achieved, the techniques further the classification process as more information associated with the inputs is received.

Abstract: Techniques and architectures for detecting the handedness of a user from touch input and suppressing unintentional touch input are described. The techniques and architectures may analyze short-lived contacts that occur on a touch surface around a same time as input from an input tool to determine a hand that a user is using to hold the input tool. An inactive region may be established for the touch surface based on the hand determination and/or contextual information related to the user, the touch surface and so on. The inactive region may allow unintentional input to be identified and suppressed.

Abstract: Techniques and architectures for detecting the handedness of a user from touch input and suppressing unintentional touch input are described. The techniques and architectures may analyze short-lived contacts that occur on a touch surface around a same time as input from an input tool to determine a hand that a user is using to hold the input tool. An inactive region may be established for the touch surface based on the hand determination and/or contextual information related to the user, the touch surface and so on. The inactive region may allow unintentional input to be identified and suppressed.

Abstract: The techniques described herein implement a classification process to evaluate information associated with a tool input (e.g., from an input tool such as a pen or a stylus) and a user touch input (e.g., from a finger or a palm of a hand) to determine whether the user touch input is an intended or an unintended touch input. The information evaluated may be associated with an arrival of the tool input relative to an arrival of the user touch input. The information evaluated may also be associated with a movement of the tool input relative to a movement of the user touch input. In various implementations, the techniques may calculate an evaluation score and compare the evaluation score to a confidence classification threshold. If a confident classification cannot be achieved, the techniques further the classification process as more information associated with the inputs is received.

Abstract: Techniques for providing input data type profiles are described. In at least some embodiments, input data type profiles can be implemented to enable applications to receive different types and/or combinations of input data. For example, input data type profiles can specify different types of input data generated based on input to a tactile input device, such as raw touch data, processed touch data, and pen input data. In at least some embodiments, techniques can be implemented to enable an application to receive multiple types of input data (e.g., combinations of touch data and/or pen input data) in parallel.

Abstract: Methods and systems for enabling a tablet input object is described. A tablet input object can take various inputs from touch, a mouse, and a pen and send their information to an application.

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

Abstract: Techniques for providing input data type profiles are described. In at least some embodiments, input data type profiles can be implemented to enable applications to receive different types and/or combinations of input data. For example, input data type profiles can specify different types of input data generated based on input to a tactile input device, such as raw touch data, processed touch data, and pen input data. In at least some embodiments, techniques can be implemented to enable an application to receive multiple types of input data (e.g., combinations of touch data and/or pen input data) in parallel.

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

Abstract: Methods and systems for enabling a tablet input object is described. A tablet input object can take various inputs from touch, a mouse, and a pen and send their information to an application.

Abstract: A system for enabling a tablet input object is described. A tablet input object can take various inputs from touch, a mouse, and a pen and send their information to an application.

Abstract: A virtual driver is enabled and a class driver is bypassed to provide at least one functionality different than that of the bypassed class driver. A filter driver is initialized in the stack of a class driver in order to bypass the class driver. The filter driver receives inputs associated with the input device and/or application emulating an input device and passes the input data to a virtual driver. The virtual driver provides data to an operating system for functionality that is at least partially different than that of the bypassed class driver.

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