Determining when a touch is processed as a mouse event
First Claim
1. A method comprising:
- identifying a user interface that corresponds to a touch event detected by a multi-touch input surface that displays the user interface;
determining, using at least one processor, that the user interface displayed on the multi-touch input surface does not accept touch events and that a touch-to-mouse adapter is available; and
in response to determining that the user interface does not accept touch events and that the touch-to mouse-adapter is available, providing the user interface with a mouse event, the mouse event being generated from the touch event by the touch-to-mouse adapter.
1 Assignment
0 Petitions
Accused Products
Abstract
A multi-touch driver handling user inputs or touches on a multi-touch input device. The method includes receiving touch data associated with a touch detected by the multi touch input device. The multi-touch driver determines a target user interface (UI) component for the touch by processing the touch data and then determines whether the target handles touch events. If so, the driver sends the touch data to the target for handling as a touch event, thereby saving a touch-to-mouse conversion for later touches. The touch may be a first touch received in a particular input region of a GUI displayed on a touch surface. The driver receives touch data for a second touch input later than the first touch but while the first touch is still active. The driver determines a target UI component for the second touch and passes the second touch data to the second target as a mouse event.
-
Citations
20 Claims
-
1. A method comprising:
-
identifying a user interface that corresponds to a touch event detected by a multi-touch input surface that displays the user interface; determining, using at least one processor, that the user interface displayed on the multi-touch input surface does not accept touch events and that a touch-to-mouse adapter is available; and in response to determining that the user interface does not accept touch events and that the touch-to mouse-adapter is available, providing the user interface with a mouse event, the mouse event being generated from the touch event by the touch-to-mouse adapter. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A non-transitory machine-readable storage medium comprising instructions that, when executed by one or more processors of a machine, cause the machine to perform operations comprising:
-
identifying a user interface that corresponds to a touch event detected by a multi-touch input surface that displays the user interface; determining, using at least one processor, that the user interface displayed on the multi-touch input surface does not accept touch events and that a touch-to-mouse adapter is available; and in response to determining that the user interface does not accept touch events and that the touch-to mouse-adapter is available, providing the user interface with a mouse event, the mouse event being generated from the touch event by the touch-to-mouse adapter. - View Dependent Claims (15, 16)
-
-
17. A system comprising:
-
a device with a multi-touch input surface configurable to display a user interface and detect a touch event that corresponds to the user interface; and a processor configured to; identify the user interface displayed on the multi-touch input surface that corresponds to the touch event detected the multi-touch input surface; determine that the user interface displayed on the multi-touch input surface does not accept touch events and that a touch-to-mouse adapter is available; and in response to determining that the user interface does not accept touch events and that the touch-to mouse-adapter is available, provide the user interface with a mouse event, the mouse event being generated from the touch event by the touch-to-mouse adapter. - View Dependent Claims (18, 19, 20)
-
Specification