DETERMINING WHEN A TOUCH IS PROCESSED AS A MOUSE EVENT

• US 20130106754A1
• Filed: 12/13/2012
• Published: 05/02/2013
• Est. Priority Date: 05/11/2009
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Kukulski, Timothy Walter
• Granted Patent: US 8,717,323 B2
• Time in Patent Office: Days
• US Class Current: 345/173
• CPC Class Codes: G06F 2203/04808 Several contacts: gestures triggering a specific function, e.g. scrolling, zooming, right-click, when the user establishes several contacts with the surface simultaneously; e.g. using several fingers or a combination of fingers and pen
• CPC Class Codes: G06F 3/041 Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
• CPC Class Codes: G06F 3/0488 using a touch-screen or digitiser, e.g. input of commands through traced gestures

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.

Claims

1. A method comprising:

identifying a user interface that corresponds to a touch event detected on an input surface that displays the user interface;

determining, using at least one processor, that the user interface does not accept touch events and that a touch-to-mouse adapter is available; and

providing the user interface with a mouse event based on the determining that the user interface does not accept touch events and that the touch-to mouse-adapter is available,

the mouse event being generated from the touch event by the touch-to-mouse adapter.

2. The method of claim 1 wherein:

the identifying of the user interface is based on a location of the touch event being within a display area that displays the user interface on the input surface.

3. The method of claim 1, wherein:

the identifying of the user interface includes comparing a location that corresponds to the touch event with a display area in which the user interface is displayed on the input surface.

4. The method of claim 1, wherein:

the determining that the user interface does not accept touch events and that the touch-to-mouse adapter is available includes determining that the user interface accepts mouse events.

5. The method of claim 1 further comprising:

generating the mouse event by processing the touch event with the touch-to-mouse adapter determined to be available.

6. The method of claim 5, wherein:

the processing of the touch event includes converting the touch into a mouse-down event.

7. The method of claim 1 further comprising:

marking the touch-to-mouse adapter as being unavailable.

8. The method of claim 7, wherein:

the marking of the touch-to-mouse adapter as being unavailable is in response to the determining that the user interface does not accept touch events.

9. The method of claim 1, wherein:

the touch event is a first touch event that indicates a start of a touch on the input surface;

the mouse event is a mouse-down event; and

the method further comprises;

detecting a second touch event that indicates an end of the touch; and

providing the user interface with a mouse-up event generated from the second touch event by the touch-to-mouse adapter.

10. The method of claim 9 further comprising:

detecting a third touch event that indicates the touch is maintained on the input surface;

providing the user interface with a mouse update generated from the third touch event by the touch-to-mouse adapter.

11. The method of claim 9 further comprising:

marking the touch-to-mouse adapter as being available in response to the providing of the mouse-up event.

12. The method of claim 1, wherein:

the touch event is a second touch event that indicates a second touch on the input surface while a first touch indicated by a first touch event is maintained on the input surface.

13. The method of claim 12 further comprising:

detecting the first touch event that indicates maintenance of the first touch on the input surface; and

identifying a further user interface that corresponds to the first touch event;

determining that the further user interface accepts touch events; and

providing the further user interface with the first touch event based on the determining that the further user interface accepts touch events.

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 on an input surface that displays the user interface;

determining that the user interface does not accept touch events and that a touch-to-mouse adapter is available; and

providing the user interface with a mouse event based on the determining that the user interface does not accept touch events and that the touch-to mouse-adapter is available,

the mouse event being generated from the touch event by e touch-to-mouse adapter.

15. The non-transitory machine-readable storage medium of claim 14, wherein the operations further comprise:

generating the mouse event by processing the touch event with the touch-to-mouse adapter determined to be available.

16. The non-transitory machine readable storage medium of claim 14, wherein the operations further comprise:

marking the touch-to-mouse adapter as being unavailable in response to the determining that the user interface does not accept touch events.

17. A system comprising:

a device with an 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 that corresponds to the touch event detected on the input surface;

determine that the user interface does not accept touch events and that a touch-to-mouse adapter is available; and

provide the user interface with a mouse event based on the determining that the user interface does not accept touch events and that the touch-to mouse-adapter is available,

the mouse event being generated from the touch event by the touch-to-mouse adapter.

18. The system of claim 17, wherein:

the processor, in determining that the user interface does not accept touch events and that the touch-to-mouse adapter is available, is configured to determine that the user interface accepts mouse events.

19. The system of claim 17, wherein:

the processor is configured to generate the mouse event by processing the touch event with the touch-to-mouse adapter determined to be available.

20. The system of claim 17, wherein:

the processor is configured to mark the touch-to-mouse adapter as being unavailable in response to a determination that the user interface does not accept touch events.