Device specific data in a unified pointer message

US9274622B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9274622-B2
Application numberUS-201213609258-A
CountryUS
Kind codeB2
Filing dateSep 11, 2012
Priority dateSep 11, 2012
Publication dateMar 1, 2016
Grant dateMar 1, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

In one embodiment, a unified pointer message 300 may describe in a single type of pointer message a coordinate input from a user via multiple types of pointer devices. An input device interface 150 may receive a coordinate input 350 from an input device. A processor 120 may execute an application programming interface layer 430 that creates a unified pointer message 300 for the coordinate input 350 . The processor 120 may send the unified pointer message 300 to an application. The processor 120 may process a device specific data set 244 unhandled by the application.

First claim

Opening claim text (preview).

We claim: 1. A machine-implemented method, comprising: receiving a coordinate input from a pointer device driver; creating a unified pointer message at an application programming interface layer representing the coordinate input from a touch input hardware and a mouse hardware as a single event type using a superset of data that is common to a plurality of pointer devices and a subset of data including a device specific data set that is specific to a pointer device among the plurality of pointer devices; sending the unified pointer message to an application; and processing the device specific data set unhandled by the application. 2. The method of claim 1 , further comprising: identifying in the unified pointer message the pointer device driver providing the coordinate input. 3. The method of claim 1 , further comprising: receiving the unhandled device specific data set from the application. 4. The method of claim 1 , further comprising: translating the unhandled device specific data set to at least one of a mouse event and a gesture event for the application. 5. The method of claim 1 , further comprising: identifying a current device specific state in the unified pointer message. 6. The method of claim 1 , further comprising: identifying a previous device specific state in the unified pointer message. 7. The method of claim 1 , further comprising: calculating a device specific data delta for the unified pointer message. 8. A tangible machine-readable medium having a set of instructions detailing a method stored thereon that when executed by one or more processors cause the one or more processors to perform the method, the method comprising: receiving a coordinate input from a pointer device driver; creating a unified pointer message at an application programming interface layer representing the coordinate input from a touch input hardware and a mouse hardware as a single event type using a superset of data that is common to a plurality of pointer devices and a subset of data including a device specific data set that is specific to a pointer device among the plurality of pointer devices; sending the unified pointer message to an application; and processing the device specific data set unhandled by the application. 9. The tangible machine-readable medium of claim 8 , wherein the method further comprises: identifying in the unified pointer message a pointer device providing the coordinate input. 10. The tangible machine-readable medium of claim 8 , wherein the method further comprises: receiving a promotion directive from the application. 11. The tangible machine-readable medium of claim 8 , wherein the method further comprises: promoting a legacy device message based on the unified pointer message. 12. The tangible machine-readable medium of claim 8 , wherein the method further comprises: identifying a current device specific state in the unified pointer message. 13. The tangible machine-readable medium of claim 8 , wherein the method further comprises: identifying a previous device specific state in the unified pointer message. 14. The tangible machine-readable medium of claim 8 , wherein the method further comprises: calculating a device specific state delta for the unified pointer message. 15. A pointer device interface, comprising: an input device interface configured to receive a coordinate input from a pointer device driver; a processor configured to execute an application programming interface layer that creates a unified pointer message representing the coordinate input from a touch input hardware and a mouse hardware as a single event type using a superset of data that is common to a plurality of pointer devices and a subset of data including a device specific data set that is specific to a pointer device among the plurality of pointer devices, send the unified pointer message to an application, and process the device specific data set unhandled by the application. 16. The pointer device interface of claim 15 , wherein the unified pointer message represents the coordinate input from at least one of a computer pen and a gesture capture device. 17. The pointer device interface of claim 15 , wherein the processor is configured to identify in the unified pointer message the pointer device driver providing the coordinate input. 18. The pointer device interface of claim 15 , wherein the processor is configured to translate the unhandled device specific data set to at least one of a mouse event and a gesture event for the application. 19. The pointer device interface of claim 15 , wherein the processor is configured to promote a legacy device message based on the unified pointer message. 20. The pointer device interface of claim 15 , wherein the processor is configured to calculate a device specific state delta for the unified pointer message.

Assignees

Inventors

Classifications

  • Execution arrangements for user interfaces · CPC title

  • Configuring for operating with peripheral devices; Loading of device drivers · CPC title

  • G06F3/038Primary

    Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry · CPC title

  • Physics · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9274622B2 cover?
In one embodiment, a unified pointer message 300 may describe in a single type of pointer message a coordinate input from a user via multiple types of pointer devices. An input device interface 150 may receive a coordinate input 350 from an input device. A processor 120 may execute an application programming interface layer 430 that creates a unified pointer message 300 for the coor…
Who is the assignee on this patent?
Wright Stephen, Yamamoto Hirofumi, Chung Pak Kiu, and 7 more
What technology area does this patent fall under?
Primary CPC classification G06F3/038. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 01 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).