Mechanism for allowing applications to filter out or opt into tablet input
First Claim
Patent Images
1. A computing system comprising:
- a digitizer;
a processor that executes a client side application having an input sink; and
a tablet input object, including a tablet context ID that specifies a tablet name, 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 a message including a signature from said digitizer that differentiates between touch input, made via a user'"'"'s finger, and pen input; and
a client side object that receives the message from the server side object, the client side object exchanging the message with said input sink of the client side application, the client side object determining that the received message represents touch input, made via a user'"'"'s finger based upon the tablet name, wherein a portion of the tablet name includes a term identifying the tablet as a touch tablet, wherein, upon a determination that touch input, made via a user'"'"'s finger, has been received, the client side application provides touch-specific options and disables areas of a user interface not affected by touch input.
2 Assignments
0 Petitions
Accused Products
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.
-
Citations
20 Claims
-
1. A computing system comprising:
-
a digitizer; a processor that executes a client side application having an input sink; and a tablet input object, including a tablet context ID that specifies a tablet name, 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 a message including a signature from said digitizer that differentiates between touch input, made via a user'"'"'s finger, and pen input; and a client side object that receives the message from the server side object, the client side object exchanging the message with said input sink of the client side application, the client side object determining that the received message represents touch input, made via a user'"'"'s finger based upon the tablet name, wherein a portion of the tablet name includes a term identifying the tablet as a touch tablet, wherein, upon a determination that touch input, made via a user'"'"'s finger, has been received, the client side application provides touch-specific options and disables areas of a user interface not affected by touch input. - View Dependent Claims (2, 3, 4)
-
-
5. A computing system comprising:
-
a digitizer responsive to touch input; and a processor that executes a client side application having an input sink, said processor supporting a tablet input object, including a tablet context ID that specifies a tablet name, 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, wherein the tablet input object includes; a server side object that receives a message including a signature from said digitizer that differentiates between touch input, made via a user'"'"'s finger, and mouse events; and a client side object that; receives the message from the server side object, the client side object exchanging the message with said input sink of said client side application, checks the tablet name and determines that the received message represents touch input, made via a user'"'"'s finger if a portion of the tablet name includes a term identifying the tablet as a touch tablet, said processor generating mouse events including a touch signature from said digitizer based on touch input, said mouse events being passed to said client side application, wherein, upon a determination from said touch signature that touch input, made via a user'"'"'s finger, has been received, the client side application provides touch-specific options. - View Dependent Claims (6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19)
-
-
20. A computing system comprising:
-
a digitizer responsive to touch input; and a processor that executes an input object that defines a plurality of different input types including touch input, made via a user'"'"'s finger, and mouse events, wherein the input object includes; a server side object that receives a message including a touch signature from the digitizer that differentiates between touch input, made via a user'"'"'s finger, and mouse events; and a client side object that receives the message from the server side object and passes the message to an application executed by the processor, wherein, the application determines that the received message represents touch input, made via a user'"'"'s finger, based upon a portion of the name associated with the input object including a term identifying the tablet as a touch tablet, and an intentional contact confidence level, that touch input, made via a user'"'"'s finger, has been received, and provides touch-specific options.
-
Specification