1 <?xml version="1.0" encoding="UTF-8"?>
2 <node xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0" name="/node">
3 <interface name="org.freedesktop.atspi.DeviceEventController">
4 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
5 <p>The interface via which clients request notification of device events, and
6 through which device events may be simulated.</p>
8 <method name="registerKeystrokeListener">
9 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
10 <p>Register to intercept keyboard events, and either pass them on or
13 <arg direction="in" name="listener" type="o" tp:type="DeviceEventListener">
15 A DeviceEventListener which will intercept key events.
18 <arg direction="in" name="keys" type="a(iisi)" tp:type="KeySet">
20 A KeySet indicating which keys to intercept, or KEYSET_ALL_KEYS.
23 <arg direction="in" name="mask" type="u" tp:type="ControllerEventMask">
25 A ControllerEventMask filtering the intercepted key events.
28 <arg direction="in" name="type" type="au" tp:type="KeyEventTypeSeq">
30 A KeyEventTypeSeq that may created by ORing event types together.
33 <arg direction="in" name="mode" type="(bbb)" tp:type="EventListenerMode">
35 An EventListenerMode indicating whether the listener should receive the events synchronously, potentially consuming them,or just be notified asynchronously of those events that havebeen generated.@note Some platforms have limited support for global, preemptive EventListenerMode.Such a registration may fail if another client already has priority for preemptiveaccess to one or more of the members of the KeySet. AT consumers have the optionof re-trying the request without the global flag, or without the preemptive flag,or of re-trying with a different KeySet. The best support for pre-emptiveglobal keyboard listeners is provided on platforms whose Xserver implementationprovides the XEvIE extension.
38 <arg direction="out" type="b" tp:type="boolean">
40 <code>True</code> if the DeviceEventListener was successfully registeredfor the requested KeySet, ControllerEventMask, event types, and EventListenerMode; otherwise returns <code>False</code>.
44 <method name="deregisterKeystrokeListener">
46 De-register a previously registered keyboard eventlistener.
48 <arg direction="in" name="listener" type="o" tp:type="DeviceEventListener">
50 A DeviceEventListener which will intercept key events.
53 <arg direction="in" name="keys" type="a(iisi)" tp:type="KeySet">
55 A KeySet indicating which keys to intercept, or KEYSET_ALL_KEYS.
58 <arg direction="in" name="mask" type="u" tp:type="ControllerEventMask">
60 A ControllerEventMask filtering the intercepted key events.
63 <arg direction="in" name="type" type="u" tp:type="KeyEventTypeSeq">
65 An EventType mask that may created by ORing event types together.
69 <method name="registerDeviceEventListener">
70 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
71 <p>Register to intercept events, and either pass them on or
72 consume them. To listen to keyboard events use registerKeystrokeListener
75 <arg direction="in" name="listener" type="o" tp:type="DeviceEventListener">
77 A DeviceEventListener which will intercept events.
80 <arg direction="in" name="types" type="u" tp:type="EventTypeSeq">
82 An EventTypeSeq indicating which event types to listen for.
85 <arg direction="out" type="b" tp:type="boolean">
87 <code>True</code> if successful, <code>False</code> if not.
91 <method name="deregisterDeviceEventListener">
93 De-register a previously registered keyboard eventlistener.
95 <arg direction="in" name="listener" type="o" tp:type="DeviceEventListener">
97 a DeviceEventListener which will intercept events.
100 <arg direction="in" name="types" type="u" tp:type="EventTypeSeq">
102 An EventTypeSeq indicating which event types to stoplistening for.
106 <method name="notifyListenersSync">
107 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
108 <p>Notify the Registry instance that a device event has taken place, and
109 allow pre-emptive listeners the opportunity to 'consume' the event
110 and thus prevent its further issuance/forwarding. This is the
111 method used by accessibility bridges to forward "toolkit dependent"
112 device events to the Registry from the application's process space. </p>
114 <p>AT clients do not normally need to use this method, it is intended for use
115 by toolkit bridges and special-purpose applications. </p>
117 <arg direction="in" name="event" type="(uinnisb)" tp:type="DeviceEvent"/>
118 <arg direction="out" type="b" tp:type="boolean">
120 <code>True</code> if the event was consumed by a (pre-emptive) listener, <code>False</code> if not (in which case the device event will be forwardedas normal to any application which would normally receive it, e.g.the currently active application in the case of mouse or keyboard events).
124 <method name="notifyListenersAsync">
125 <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
126 <p>Notify the Registry instance that a device event has taken place in
127 an asynchronous manner. This is the
128 method used by accessibility bridges to forward "toolkit dependent"
129 device events to the Registry from the application's process space.
130 If the event in question is potentially pre-emptible.
131 notifyListenersSync should be used instead. </p>
133 <p>AT clients do not normally need to use this method, it is intended for use
134 by toolkit bridges and special-purpose applications.</p>
136 <arg direction="in" name="event" type="(uinnisb)" tp:type="DeviceEvent"/>
138 <method name="generateKeyboardEvent">
140 Synthesize a keyboard event.
142 <arg direction="in" name="keycode" type="i">
144 A long integer indicating the keycode ofthe keypress to be synthesized.
147 <arg direction="in" name="keystring" type="s">
149 An optional UTF-8 string indicating a complexkeyboard input event.
152 <arg direction="in" name="type" type="u" tp:type="KeySynthType">
154 <p>A KeySynthType indicating the type of event(s) to be synthesized: a key press, release, press-release pair,or a complex input string (for instance from aninternationalized or complex text input method, ora composed character).</p>
156 <p>Keycode may be truncated before beingprocessed, as keycode length may be platform-dependentand keycode ranges are generally much smaller thanCORBA_long. One or the other of keycode or keystring are generally NULL, (but not both), depending on the value of <code>type</code>.</p>
160 <method name="generateMouseEvent">
162 Synthesize a mouse event.
164 <arg direction="in" name="x" type="i">
166 A long integer indicating the screen x coord for the mouse event.
169 <arg direction="in" name="y" type="i">
171 A long integer indicating the screen y coord for the mouse event.
174 <arg direction="in" name="eventName" type="s">
176 A string indicating the type of mouse event, e.g. "button1up"