Window Server Event Taps
First Claim
1. A programmable processing device including:
- a processor;
a window server application executing on the processor;
a user interface event application programming interface (API) to the window server application, the API comprising;
a function allowing a user to register each of a plurality of event processing routines within the window server application, wherein each event processing routine—
is registered at a specified one of a plurality of user interface event taps within the window server application,is associated with a specified user interface event type,is not associated with a specific application being presented by the window server application, andis invoked for execution by the window server application when a first event of the associated user interface event type is received by the window server application at the specified one of a plurality of user interface event taps prior to notifying one or more applications being presented by the window server application that the specified user interface event type was received by the window server application.
0 Assignments
0 Petitions
Accused Products
Abstract
Methods, devices and an associated application programming interface are described that permits a user to register event tap routines (“ETRs”) with an application such as, for example, a window server application. Event tap routines permit events such as human interface device events to be processed at multiple points and in a manner not provided during normal window server operations. Event tap routines may effect passive or active event responses. Passive ETRs may merely record the occurrence of an event or the time between successive events without modifying or altering the event'"'"'s processing sequence within a window server. Active ETRs, on the other hand, effect some programmatic response to an event. For example, active ETRs may modify the state of an event, delete the event, create one or more additional events or cause the event to be processed “out of sequence” by the window server application.
20 Citations
69 Claims
-
1. A programmable processing device including:
-
a processor; a window server application executing on the processor; a user interface event application programming interface (API) to the window server application, the API comprising; a function allowing a user to register each of a plurality of event processing routines within the window server application, wherein each event processing routine— is registered at a specified one of a plurality of user interface event taps within the window server application, is associated with a specified user interface event type, is not associated with a specific application being presented by the window server application, and is invoked for execution by the window server application when a first event of the associated user interface event type is received by the window server application at the specified one of a plurality of user interface event taps prior to notifying one or more applications being presented by the window server application that the specified user interface event type was received by the window server application. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A storage device comprising instructions stored thereon and readable by a programmable control device, the instructions embodying a user interface event application programming interface (API) to a window server application, the API comprising:
-
a function allowing a user to register each of a plurality of event processing routines within the window server application, wherein each event processing routine— is registered at a specified one of a plurality of user interface event taps within the window server application, is associated with a specified user interface event type, is not associated with a specific application being presented by the window server application, and is invoked for execution by the window server application when a first event of the associated user interface event type is received by the window server application at the specified one of a plurality of user interface event taps prior to notifying one or more applications being presented by the window server application that the specified user interface event type was received by the window server application.
-
-
11. A computer system, comprising:
-
a display device; one or more input devices; a processor operatively coupled to the display and input devices; and memory operatively coupled to the processor, input and display devices, said memory adapted to store instructions embodying a user interface event application programming interface (API) to a window server application, the API comprising; a function allowing a user to register each of a plurality of event processing routines within the window server application, wherein each event processing routine— is registered at a specified one of a plurality of user interface event taps within the window server application, is associated with a specified user interface event type, is not associated with a specific application being presented by the window server application, and is invoked for execution by the window server application when a first event of the associated user interface event type is received by the window server application at the specified one of a plurality of user interface event taps prior to notifying one or more applications being presented by the window server application that the specified user interface event type was received by the window server application.
-
-
12. A computer event processing method, the method comprising:
-
receiving a first event at a registered event processing routine executing on a programmable control device wherein the first event is targeted for a first application; identifying the first event as belonging to at least one of a plurality of event types; determining the first event is associated with an event processing routine; causing the event processing routine to process the first event without regard to the first application; receiving a result event from the event processing routine; and providing the result event for delivery to the first application, wherein the acts of receiving an event, identifying, determining, causing and receiving a result event are performed by the programmable control device prior to providing the result event for delivery to the first application. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20)
-
-
21. A user interface event processing method performed by a programmable control device, the method comprising:
-
receiving a user interface event from an operating system controlling a programmable control device, the user interface event targeted for a first application; identifying the user interface event as belonging to at least one of a plurality of user interface event types; determining the user interface event is associated with an event processing routine; causing the event processing routine to process the user interface event without regard to the first application; receiving a result from the event processing routine; and dispatching the result to the first application. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37)
-
-
38. A user interface event processing method performed by a programmable control device, the method comprising:
-
receiving a user interface event from an operating system controlling the programmable control device, the user interface event associated with a window, the window associated with a first application; identifying the user interface event as belonging to at least one of a plurality of registered user interface event types; determining the user interface event is associated with an event processing routine; causing the associated event processing routine to execute without regard to the first application; receiving a result event from the event processing routine; and delivering the result event to the window. - View Dependent Claims (39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54)
-
-
55. An event processing method, the method comprising:
-
receiving a first event targeted for an application; associating the first event with a plurality of event types; associating at least one event processing routing with each of the plurality of event types; causing at least said one event processing routine to process the first event, without regard to the application, to generate a second event; and delivering the second event to the application. - View Dependent Claims (56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69)
-
Specification