Touch input data handling

• US 7,928,964 B2
• Filed: 05/21/2006
• Issued: 04/19/2011
• Est. Priority Date: 04/22/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kolmykov-Zotov, Alexander J., Dodge, Steven P., Townsend, Reed L., Scott, Bryan D.
• Primary Examiner(s): Mengistu; Amare
• Assistant Examiner(s): Bolotin; Dmitriy
• Application Number:
  US11/419,496
• Publication Number:
  US 20060267957A1
• Time in Patent Office: 1,794 Days
• Field of Search: 345156-184, 178/18.01, 178/18.02, 178/18.03
• US Class Current: 345/173
• CPC Class Codes: G06F 3/03545 Pens or stylus
• 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/0416 Control or interface arrangements specially adapted for digitisers

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 sends their information to an application or operating system. Also, a pen message pathway may also be used to handle touch messages, thereby reusing an existing pen message pathway for messages created by something other than a pen.

Claims

1. A computing system comprising:

a processor that executes a client side application; and

a tablet input object that defines a plurality of different input types including touch input, made via a user'"'"'s finger, and pen input, wherein the computing system provides a corresponding set of options for each of the plurality of different input types, the tablet input object including;

a server side object that receives input information from a digitizer; and

a client side object that;

receives the input information from the server side object, the client side object exchanging the input information with said client side application,

determines an input type using one or more signatures of input messages,

uses a contact area, indicating a width and a height of an area that is contacted by the user'"'"'s finger or the user'"'"'s palm, to determine if the touch input is accidental input or intentional input wherein the client side object distinguishes between a first contact area that is sufficiently small to indicate intentional contact by the user'"'"'s finger and a second contact area that is not sufficiently small to indicate intentional contact by the user'"'"'s finger, the second contact area indicating accidental contact by the user'"'"'s palm, wherein accidental input is ignored, and processes the input information based upon a determined input type, including providing one or more options of the set of options corresponding to the determined input type.

2. The computing system according to claim 1, wherein the client side object of said tablet input object exchanges the input information with said client side application using out of process remote procedure calls.

3. The computing system according to claim 1, wherein the client side object further uses a contact pressure to determine if touch input is accidental input or intentional input.

4. A computing system comprising:

a digitizer responsive to touch input; and

a processor supporting a tablet input object that defines a plurality of different input types including touch input, made via a user'"'"'s finger, and mouse events, wherein the computing system provides a corresponding set of options for each of the plurality of different input types, the tablet input object including a server side object that receives information from said digitizer, the information including touch input and additional information, and a client side object that receives the information from the server side object, the client side object exchanging the information with a client side application and that uses a contact area, indicating a width and a height of an area that is contacted by the user'"'"'s finger or the user'"'"'s palm, to determine if the touch input is accidental input or intentional input, wherein the client side object distinguishes between a first contact area that is sufficiently small to indicate intentional contact by the user'"'"'s finger and a second contact area that is not sufficiently small to indicate intentional contact by the user'"'"'s finger, the second contact area indicating accidental contact by the user'"'"'s palm, wherein accidental input is ignored, said processor generating mouse events based on information from said digitizer based on touch input, made via the user'"'"'s finger, said mouse events being passed to said client side application, said client side application using the additional information to make touch-specific modifications to the client side application.

5. The computing system according to claim 4, said processor modifying a user interface when said mouse events were created from touch input to said digitizer.

6. The computing system according to claim 5, said processor modifying said user interface to include larger grab handles for visual objects.

7. The computing system according to claim 5, said processor modifying said user interface to prevent touch from controlling at least a part of said user interface.

8. The computing system according to claim 4, said processor including an inking client, said processor restarting said inking client.

9. The computing system according to claim 4, said processor including an application programming interface that allows programmatical control when touch is enabled.

10. The computing system according to claim 4, said processor including an application programming interface that allows said processor to handle touch messages as pen messages yet also differentiates the touch and pen messages through an extended signature of the messages.

11. The computing system according to claim 4, said processor including an application programming interface that allows control of touch modes.

12. The computing system according to claim 4, said processor including an application programming interface that allows touch input to be disabled.

13. The computing system according to claim 12, said application programming interface permitting disabling of touch input when additional information in messages indicates touch should be disabled.

14. The computing system according to claim 12, said application programming interface permitting disabling of touch input when a request to disable touch comes from a touch ink stream.

15. The computing system according to claim 12, said application programming interface allowing touch input to be handled as both pen input and mouse input.

16. The computing system according to claim 12, said application programming interface exchanging information using a shared memory.

17. The computing system according to claim 4, wherein the client side application further uses a contact pressure to determine if touch input is accidental input or intentional input.