|
428
|
1 /* Definitions for the new event model;
|
|
|
2 created 16-jul-91 by Jamie Zawinski
|
|
|
3 Copyright (C) 1991, 1992, 1993 Free Software Foundation, Inc.
|
|
|
4 Copyright (C) 1995, 1996 Ben Wing.
|
|
|
5
|
|
|
6 This file is part of XEmacs.
|
|
|
7
|
|
|
8 XEmacs is free software; you can redistribute it and/or modify it
|
|
|
9 under the terms of the GNU General Public License as published by the
|
|
|
10 Free Software Foundation; either version 2, or (at your option) any
|
|
|
11 later version.
|
|
|
12
|
|
|
13 XEmacs is distributed in the hope that it will be useful, but WITHOUT
|
|
|
14 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
|
|
15 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
|
|
|
16 for more details.
|
|
|
17
|
|
|
18 You should have received a copy of the GNU General Public License
|
|
|
19 along with XEmacs; see the file COPYING. If not, write to
|
|
|
20 the Free Software Foundation, Inc., 59 Temple Place - Suite 330,
|
|
|
21 Boston, MA 02111-1307, USA. */
|
|
|
22
|
|
|
23 /* Synched up with: Not in FSF. */
|
|
|
24
|
|
440
|
25 #ifndef INCLUDED_events_h_
|
|
|
26 #define INCLUDED_events_h_
|
|
428
|
27
|
|
|
28 #include "systime.h"
|
|
|
29
|
|
|
30 /* There is one object called an event_stream. This object contains
|
|
|
31 callback functions for doing the window-system-dependent operations
|
|
|
32 that XEmacs requires.
|
|
|
33
|
|
|
34 If XEmacs is compiled with support for X11 and the X Toolkit, then this
|
|
|
35 event_stream structure will contain functions that can cope with input
|
|
|
36 on XEmacs windows on multiple displays, as well as input from dumb tty
|
|
|
37 frames.
|
|
|
38
|
|
|
39 If it is desired to have XEmacs able to open frames on the displays of
|
|
|
40 multiple heterogeneous machines, X11 and SunView, or X11 and NeXT, for
|
|
|
41 example, then it will be necessary to construct an event_stream structure
|
|
|
42 that can cope with the given types. Currently, the only implemented
|
|
440
|
43 event_streams are for dumb-ttys, and for X11 plus dumb-ttys,
|
|
|
44 and for mswindows.
|
|
428
|
45
|
|
|
46 To implement this for one window system is relatively simple.
|
|
|
47 To implement this for multiple window systems is trickier and may
|
|
|
48 not be possible in all situations, but it's been done for X and TTY.
|
|
|
49
|
|
|
50 Note that these callbacks are *NOT* console methods; that's because
|
|
|
51 the routines are not specific to a particular console type but must
|
|
|
52 be able to simultaneously cope with all allowable console types.
|
|
|
53
|
|
|
54 The slots of the event_stream structure:
|
|
|
55
|
|
|
56 next_event_cb A function which fills in an XEmacs_event structure
|
|
|
57 with the next event available. If there is no event
|
|
|
58 available, then this should block.
|
|
|
59
|
|
|
60 IMPORTANT: timer events and especially process
|
|
|
61 events *must not* be returned if there are
|
|
|
62 events of other types available; otherwise you
|
|
|
63 can end up with an infinite loop in Fdiscard_input().
|
|
|
64
|
|
|
65 event_pending_cb A function which says whether there are events to be
|
|
|
66 read. If called with an argument of 0, then this
|
|
|
67 should say whether calling the next_event_cb will
|
|
|
68 block. If called with an argument of 1, then this
|
|
|
69 should say whether there are user-generated events
|
|
|
70 pending (that is, keypresses or mouse-clicks). This
|
|
|
71 is used for redisplay optimization, among other
|
|
|
72 things. On dumb ttys, these two results are the
|
|
|
73 same, but under a window system, they are not.
|
|
|
74
|
|
|
75 If this function is not sure whether there are events
|
|
|
76 to be read, it *must* return 0. Otherwise various
|
|
|
77 undesirable effects will occur, such as redisplay
|
|
|
78 not occurring until the next event occurs.
|
|
|
79
|
|
|
80 handle_magic_event_cb XEmacs calls this with an event structure which
|
|
|
81 contains window-system dependent information that
|
|
|
82 XEmacs doesn't need to know about, but which must
|
|
|
83 happen in order. If the next_event_cb never returns
|
|
|
84 an event of type "magic", this will never be used.
|
|
|
85
|
|
|
86 add_timeout_cb Called with an EMACS_TIME, the absolute time at
|
|
|
87 which a wakeup event should be generated; and a
|
|
|
88 void *, which is an arbitrary value that will be
|
|
|
89 returned in the timeout event. The timeouts
|
|
|
90 generated by this function should be one-shots:
|
|
|
91 they fire once and then disappear. This callback
|
|
|
92 should return an int id-number which uniquely
|
|
|
93 identifies this wakeup. If an implementation
|
|
|
94 doesn't have microseconds or millisecond
|
|
|
95 granularity, it should round up to the closest
|
|
|
96 value it can deal with.
|
|
|
97
|
|
|
98 remove_timeout_cb Called with an int, the id number of a wakeup to
|
|
|
99 discard. This id number must have been returned by
|
|
|
100 the add_timeout_cb. If the given wakeup has
|
|
|
101 already expired, this should do nothing.
|
|
|
102
|
|
|
103 select_process_cb These callbacks tell the underlying implementation to
|
|
|
104 unselect_process_cb add or remove a file descriptor from the list of fds
|
|
|
105 which are polled for inferior-process input. When
|
|
|
106 input becomes available on the given process
|
|
|
107 connection, an event of type "process" should be
|
|
|
108 generated.
|
|
|
109
|
|
|
110 select_console_cb These callbacks tell the underlying implementation
|
|
|
111 unselect_console_cb to add or remove a console from the list of consoles
|
|
|
112 which are polled for user-input.
|
|
|
113
|
|
|
114 select_device_cb These callbacks are used by Unixoid event loops
|
|
|
115 unselect_device_cb (those that use select() and file descriptors and
|
|
|
116 have a separate input fd per device).
|
|
|
117
|
|
|
118 create_stream_pair_cb These callbacks are called by process code to
|
|
|
119 delete_stream_pair_cb create and delete a pair of input and output lstreams
|
|
|
120 which are used for subprocess I/O.
|
|
|
121
|
|
|
122 quitp_cb A handler function called from the `QUIT' macro which
|
|
|
123 should check whether the quit character has been
|
|
|
124 typed. On systems with SIGIO, this will not be called
|
|
|
125 unless the `sigio_happened' flag is true (it is set
|
|
|
126 from the SIGIO handler).
|
|
|
127
|
|
|
128 XEmacs has its own event structures, which are distinct from the event
|
|
|
129 structures used by X or any other window system. It is the job of the
|
|
|
130 event_stream layer to translate to this format.
|
|
|
131 */
|
|
|
132
|
|
|
133 /*
|
|
|
134 Stream pairs description
|
|
|
135 ------------------------
|
|
|
136
|
|
|
137 Since there are many possible processes/event loop combinations, the event code
|
|
|
138 is responsible for creating an appropriate lstream type. The process
|
|
|
139 implementation does not care about that implementation.
|
|
|
140
|
|
|
141 The Create stream pair function is passed two void* values, which identify
|
|
|
142 process-dependent 'handles'. The process implementation uses these handles
|
|
|
143 to communicate with child processes. The function must be prepared to receive
|
|
440
|
144 handle types of any process implementation. Since only one process
|
|
428
|
145 implementation exists in a particular XEmacs configuration, preprocessing
|
|
440
|
146 is a means of compiling in the support for the code which deals with particular
|
|
428
|
147 handle types.
|
|
|
148
|
|
|
149 For example, a unixoid type loop, which relies on file descriptors, may be
|
|
|
150 asked to create a pair of streams by a unix-style process implementation.
|
|
|
151 In this case, the handles passed are unix file descriptors, and the code
|
|
|
152 may deal with these directly. Although, the same code may be used on Win32
|
|
|
153 system with X-Windows. In this case, Win32 process implementation passes
|
|
|
154 handles of type HANDLE, and the create_stream_pair function must call
|
|
|
155 appropriate function to get file descriptors given HANDLEs, so that these
|
|
|
156 descriptors may be passed to XtAddInput.
|
|
|
157
|
|
|
158 The handle given may have special denying value, in which case the
|
|
|
159 corresponding lstream should not be created.
|
|
|
160
|
|
|
161 The return value of the function is a unique stream identifier. It is used
|
|
|
162 by processes implementation, in its platform-independent part. There is
|
|
|
163 the get_process_from_usid function, which returns process object given its
|
|
|
164 USID. The event stream is responsible for converting its internal handle
|
|
|
165 type into USID.
|
|
|
166
|
|
|
167 Example is the TTY event stream. When a file descriptor signals input, the
|
|
|
168 event loop must determine process to which the input is destined. Thus,
|
|
|
169 the implementation uses process input stream file descriptor as USID, by
|
|
|
170 simply casting the fd value to USID type.
|
|
|
171
|
|
|
172 There are two special USID values. One, USID_ERROR, indicates that the stream
|
|
|
173 pair cannot be created. The second, USID_DONTHASH, indicates that streams are
|
|
|
174 created, but the event stream does not wish to be able to find the process
|
|
|
175 by its USID. Specifically, if an event stream implementation never calls
|
|
|
176 get_process_from_usid, this value should always be returned, to prevent
|
|
|
177 accumulating useless information on USID to process relationship.
|
|
|
178 */
|
|
|
179
|
|
|
180 /* typedef unsigned int USID; in lisp.h */
|
|
|
181 #define USID_ERROR ((USID)-1)
|
|
|
182 #define USID_DONTHASH ((USID)0)
|
|
|
183
|
|
|
184
|
|
|
185 struct event_stream
|
|
|
186 {
|
|
|
187 int (*event_pending_p) (int);
|
|
440
|
188 void (*next_event_cb) (Lisp_Event *);
|
|
|
189 void (*handle_magic_event_cb) (Lisp_Event *);
|
|
428
|
190 int (*add_timeout_cb) (EMACS_TIME);
|
|
|
191 void (*remove_timeout_cb) (int);
|
|
|
192 void (*select_console_cb) (struct console *);
|
|
|
193 void (*unselect_console_cb) (struct console *);
|
|
440
|
194 void (*select_process_cb) (Lisp_Process *);
|
|
|
195 void (*unselect_process_cb) (Lisp_Process *);
|
|
428
|
196 void (*quit_p_cb) (void);
|
|
442
|
197 void (*force_event_pending) (struct frame* f);
|
|
428
|
198 USID (*create_stream_pair_cb) (void* /* inhandle*/, void* /*outhandle*/ ,
|
|
|
199 Lisp_Object* /* instream */,
|
|
|
200 Lisp_Object* /* outstream */,
|
|
|
201 int /* flags */);
|
|
|
202 USID (*delete_stream_pair_cb) (Lisp_Object /* instream */,
|
|
|
203 Lisp_Object /* outstream */);
|
|
442
|
204 int (*current_event_timestamp_cb) (struct console *);
|
|
428
|
205 };
|
|
|
206
|
|
|
207 /* Flags for create_stream_pair_cb() FLAGS parameter */
|
|
|
208 #define STREAM_PTY_FLUSHING 0x0001
|
|
|
209 #define STREAM_NETWORK_CONNECTION 0x0002
|
|
|
210
|
|
|
211 extern struct event_stream *event_stream;
|
|
|
212
|
|
|
213 typedef enum emacs_event_type
|
|
|
214 {
|
|
|
215 empty_event,
|
|
|
216 key_press_event,
|
|
|
217 button_press_event,
|
|
|
218 button_release_event,
|
|
|
219 pointer_motion_event,
|
|
|
220 process_event,
|
|
|
221 timeout_event,
|
|
|
222 magic_event,
|
|
|
223 magic_eval_event,
|
|
|
224 eval_event,
|
|
|
225 misc_user_event,
|
|
|
226 dead_event
|
|
|
227 } emacs_event_type;
|
|
|
228
|
|
|
229 #define first_event_type empty_event
|
|
|
230 #define last_event_type dead_event
|
|
|
231
|
|
771
|
232 #ifdef MULE
|
|
|
233
|
|
|
234 enum alternative_key_chars
|
|
|
235 {
|
|
|
236 KEYCHAR_CURRENT_LANGENV,
|
|
|
237 KEYCHAR_DEFAULT_USER,
|
|
|
238 KEYCHAR_DEFAULT_SYSTEM,
|
|
|
239 KEYCHAR_UNDERLYING_VIRTUAL_KEY_CURRENT_LANGENV,
|
|
|
240 KEYCHAR_UNDERLYING_VIRTUAL_KEY_DEFAULT_USER,
|
|
|
241 KEYCHAR_UNDERLYING_VIRTUAL_KEY_DEFAULT_SYSTEM,
|
|
|
242 KEYCHAR_QWERTY,
|
|
|
243 KEYCHAR_LAST
|
|
|
244 };
|
|
|
245
|
|
|
246 #endif /* MULE */
|
|
428
|
247
|
|
|
248 struct key_data
|
|
|
249 {
|
|
771
|
250 /* What keysym this is; a character or a symbol. */
|
|
|
251 Lisp_Object keysym;
|
|
|
252 /* Modifiers held down when key was pressed: control, meta, etc.
|
|
|
253 Also includes buttons. For many keys, Shift is not a bit; that
|
|
|
254 is implicit in the keyboard layout. */
|
|
|
255 int modifiers;
|
|
|
256 #ifdef MULE
|
|
|
257 /* Alternate character interpretations for this key in different
|
|
|
258 keyboard layouts. This deals with the problem of pressing C-x in
|
|
|
259 the Russian layout (the so-called "Russian C-x problem"), for
|
|
|
260 example: `x' gets mapped to a Cyrillic character, so what do we
|
|
|
261 do? For that matter, what about `C-x b'? What we do is look the
|
|
|
262 key up in the default locales (current language environment, user
|
|
|
263 default, system default), then check to see if the underlying
|
|
|
264 virtual key is alphabetic in the same three defaults, then
|
|
|
265 finally check US ASCII. We ignore the underlying virtual key for
|
|
|
266 the current layout to avoid the problem of a French speaker
|
|
|
267 (AZERTY layout) who temporarily switches to Russian: The virtual
|
|
|
268 keys underlying Russian are US-ASCII, so what the French speaker
|
|
|
269 things of as C-a (the key just to the right of TAB) appears as
|
|
|
270 C-q. (#### We should probably ignore the current char and look
|
|
|
271 *ONLY* in alt_keychars for all control keys. What about the
|
|
|
272 English speaker who temporarily switches to the French layout and
|
|
|
273 finds C-q mapped to C-a?) */
|
|
|
274 Emchar alt_keychars[KEYCHAR_LAST];
|
|
|
275 #endif /* MULE */
|
|
428
|
276 };
|
|
|
277
|
|
|
278 struct button_data
|
|
|
279 {
|
|
771
|
280 /* What button went down or up. */
|
|
|
281 int button;
|
|
|
282 /* Bucky-bits on that button: shift, control, meta, etc. Also
|
|
|
283 includes other buttons (not the one pressed). */
|
|
|
284 int modifiers;
|
|
|
285 /* Where it was at the button-state-change (in pixels). */
|
|
|
286 int x, y;
|
|
428
|
287 };
|
|
|
288
|
|
|
289 struct motion_data
|
|
|
290 {
|
|
771
|
291 /* Where it was after it moved (in pixels). */
|
|
|
292 int x, y;
|
|
|
293 /* Bucky-bits down when the motion was detected. */
|
|
|
294 int modifiers;
|
|
428
|
295 };
|
|
|
296
|
|
|
297 struct process_data
|
|
|
298 {
|
|
771
|
299 /* the XEmacs "process" object in question */
|
|
|
300 Lisp_Object process;
|
|
428
|
301 };
|
|
|
302
|
|
|
303 struct timeout_data
|
|
|
304 {
|
|
771
|
305 /*
|
|
|
306 interval_id The ID returned when the associated call to
|
|
|
307 add_timeout_cb() was made
|
|
|
308 ------ the rest of the fields are filled in by XEmacs -----
|
|
|
309 id_number The XEmacs timeout ID for this timeout (more
|
|
|
310 than one timeout event can have the same value
|
|
|
311 here, since XEmacs timeouts, as opposed to
|
|
|
312 add_timeout_cb() timeouts, can resignal
|
|
|
313 themselves)
|
|
|
314 function An elisp function to call when this timeout is
|
|
|
315 processed.
|
|
|
316 object The object passed to that function.
|
|
|
317 */
|
|
|
318 int interval_id;
|
|
|
319 int id_number;
|
|
|
320 Lisp_Object function;
|
|
|
321 Lisp_Object object;
|
|
428
|
322 };
|
|
|
323
|
|
|
324 struct eval_data
|
|
|
325 {
|
|
771
|
326 /* This kind of event is used internally; sometimes the window system
|
|
|
327 interface would like to inform XEmacs of some user action (such as
|
|
|
328 focusing on another frame) but needs that to happen synchronously
|
|
|
329 with the other user input, like keypresses. This is useful when
|
|
|
330 events are reported through callbacks rather than in the standard
|
|
|
331 event stream.
|
|
|
332
|
|
|
333 function An elisp function to call with this event object.
|
|
|
334 object Argument of function.
|
|
|
335 */
|
|
|
336 Lisp_Object function;
|
|
|
337 Lisp_Object object;
|
|
428
|
338 };
|
|
|
339
|
|
|
340 struct misc_user_data
|
|
|
341 {
|
|
771
|
342 /* #### The misc-user type is serious junk. It should be separated
|
|
|
343 out into different events. There's no reason to create
|
|
|
344 sub-subtypes of events.
|
|
|
345
|
|
|
346 function An elisp function to call with this event object.
|
|
|
347 object Argument of function.
|
|
|
348 button What button went down or up.
|
|
|
349 modifiers Bucky-bits on that button: shift, control, meta, etc.
|
|
|
350 x, y Where it was at the button-state-change (in pixels).
|
|
|
351 This is similar to an eval_event, except that it is
|
|
|
352 generated by user actions: selections in the
|
|
|
353 menubar, scrollbar actions, or drag and drop actions.
|
|
|
354 It is a "command" event, like key and mouse presses
|
|
|
355 (and unlike mouse motion, process output, and enter
|
|
|
356 and leave window hooks). In many ways, eval_events
|
|
|
357 are not the same as keypresses or misc_user_events.
|
|
|
358 The button, modifiers, x, and y parts are only used
|
|
|
359 by the XEmacs Drag'n'Drop system. Don't depend on their
|
|
|
360 values for other types of misc_user_events.
|
|
|
361 */
|
|
|
362 Lisp_Object function;
|
|
|
363 Lisp_Object object;
|
|
|
364 int button;
|
|
|
365 int modifiers;
|
|
|
366 int x, y;
|
|
428
|
367 };
|
|
|
368
|
|
|
369 struct magic_eval_data
|
|
|
370 {
|
|
771
|
371 /* This is like an eval event but its contents are not
|
|
|
372 Lisp-accessible. This allows for "internal eval events" that call
|
|
|
373 non-Lisp-accessible functions. Externally, a magic_eval_event just
|
|
|
374 appears as a magic_event; the Lisp programmer need not know
|
|
|
375 anything more.
|
|
|
376
|
|
|
377 internal_function An unexported function to call with this event
|
|
|
378 object. This allows eval events to call internal
|
|
|
379 functions. For a normal eval event, this field
|
|
|
380 will always be 0.
|
|
|
381 object Argument of function.
|
|
|
382
|
|
|
383 */
|
|
|
384 void (*internal_function) (Lisp_Object);
|
|
|
385 Lisp_Object object;
|
|
428
|
386 };
|
|
|
387
|
|
|
388 #if defined (HAVE_X_WINDOWS) && defined(emacs)
|
|
|
389 # include <X11/Xlib.h>
|
|
|
390 #endif
|
|
|
391
|
|
462
|
392 #ifdef HAVE_GTK
|
|
|
393 #include <gdk/gdk.h>
|
|
|
394 #endif
|
|
|
395
|
|
428
|
396 union magic_data
|
|
|
397 {
|
|
771
|
398 /* No user-serviceable parts within. This is for things like
|
|
|
399 KeymapNotify and ExposeRegion events and so on that XEmacs itself
|
|
|
400 doesn't care about, but which it must do something with for proper
|
|
|
401 interaction with the window system.
|
|
|
402
|
|
|
403 Magic_events are handled somewhat asynchronously, just like
|
|
|
404 subprocess filters. However, occasionally a magic_event needs to
|
|
|
405 be handled synchronously; in that case, the asynchronous handling
|
|
|
406 of the magic_event will push an eval_event back onto the queue,
|
|
|
407 which will be handled synchronously later. This is one of the
|
|
|
408 reasons why eval_events exist; I'm not entirely happy with this
|
|
|
409 aspect of this event model.
|
|
|
410 */
|
|
|
411
|
|
428
|
412 #ifdef HAVE_TTY
|
|
771
|
413 char underlying_tty_event;
|
|
428
|
414 #endif
|
|
462
|
415 #ifdef HAVE_GTK
|
|
771
|
416 GdkEvent underlying_gdk_event;
|
|
462
|
417 #endif
|
|
428
|
418 #ifdef HAVE_X_WINDOWS
|
|
771
|
419 XEvent underlying_x_event;
|
|
428
|
420 #endif
|
|
|
421 #ifdef HAVE_MS_WINDOWS
|
|
771
|
422 int underlying_mswindows_event;
|
|
428
|
423 #endif
|
|
|
424 };
|
|
|
425
|
|
|
426 struct Lisp_Timeout
|
|
|
427 {
|
|
432
|
428 struct lcrecord_header header;
|
|
428
|
429 int id; /* Id we use to identify the timeout over its lifetime */
|
|
|
430 int interval_id; /* Id for this particular interval; this may
|
|
771
|
431 be different each time the timeout is
|
|
|
432 signalled.*/
|
|
428
|
433 Lisp_Object function, object; /* Function and object associated
|
|
771
|
434 with timeout. */
|
|
428
|
435 EMACS_TIME next_signal_time; /* Absolute time when the timeout
|
|
771
|
436 is next going to be signalled. */
|
|
428
|
437 unsigned int resignal_msecs; /* How far after the next timeout
|
|
771
|
438 should the one after that
|
|
|
439 occur? */
|
|
428
|
440 };
|
|
440
|
441 typedef struct Lisp_Timeout Lisp_Timeout;
|
|
428
|
442
|
|
440
|
443 DECLARE_LRECORD (timeout, Lisp_Timeout);
|
|
|
444 #define XTIMEOUT(x) XRECORD (x, timeout, Lisp_Timeout)
|
|
428
|
445 #define XSETTIMEOUT(x, p) XSETRECORD (x, p, timeout)
|
|
617
|
446 #define wrap_timeout(p) wrap_record (p, timeout)
|
|
428
|
447 #define TIMEOUTP(x) RECORDP (x, timeout)
|
|
|
448 #define CHECK_TIMEOUT(x) CHECK_RECORD (x, timeout)
|
|
|
449 #define CONCHECK_TIMEOUT(x) CONCHECK_RECORD (x, timeout)
|
|
|
450
|
|
|
451 struct Lisp_Event
|
|
|
452 {
|
|
|
453 /* header->next (aka XEVENT_NEXT ()) is used as follows:
|
|
|
454 - For dead events, this is the next dead one.
|
|
|
455 - For events on the command_event_queue, the next one on the queue.
|
|
|
456 - Likewise for events chained in the command builder.
|
|
|
457 - Otherwise it's Qnil.
|
|
|
458 */
|
|
|
459 struct lrecord_header lheader;
|
|
771
|
460 Lisp_Object next;
|
|
|
461 emacs_event_type event_type;
|
|
|
462
|
|
|
463 /* Where this event occurred on. This will be a frame, device,
|
|
|
464 console, or nil, depending on the event type. It is important
|
|
|
465 that an object of a more specific type than is actually generated
|
|
|
466 is not substituted -- e.g. there should not be a frame inserted
|
|
|
467 when a key-press event occurs, because events on dead channels
|
|
|
468 are automatically ignored.
|
|
|
469
|
|
|
470 Specifically:
|
|
|
471
|
|
|
472 -- for button and mouse-motion events, channel will be a
|
|
|
473 frame. (The translation to a window occurs later.)
|
|
|
474
|
|
|
475 -- for keyboard events, channel will be a console. Note that
|
|
|
476 fake keyboard events (generated by `character-to-event' or
|
|
|
477 something that calls this, such as macros) need to have the
|
|
|
478 selected console stored into them when the event is created.
|
|
|
479 This is so that the correct console-local variables (e.g. the
|
|
|
480 command builder) will get affected.
|
|
|
481
|
|
|
482 -- for timer, process, magic-eval, and eval events, channel will
|
|
|
483 be nil.
|
|
|
484
|
|
|
485 -- for misc-user events, channel will be a frame.
|
|
|
486
|
|
|
487 -- for magic events, channel will be a frame (usually) or a
|
|
|
488 device. */
|
|
|
489 Lisp_Object channel;
|
|
|
490
|
|
|
491 /* When this event occurred -- if not known, this is made up. ####
|
|
|
492 All timestamps should be measured as milliseconds since XEmacs
|
|
|
493 started. Currently they are raw server timestamps. (The X
|
|
|
494 protocol doesn't provide any easy way of translating between
|
|
|
495 server time and real process time; yuck.) */
|
|
|
496
|
|
|
497 unsigned int timestamp;
|
|
428
|
498 union
|
|
|
499 {
|
|
771
|
500 struct key_data key;
|
|
|
501 struct button_data button;
|
|
|
502 struct motion_data motion;
|
|
|
503 struct process_data process;
|
|
|
504 struct timeout_data timeout;
|
|
|
505 struct eval_data eval; /* misc_user_event no longer uses this */
|
|
|
506 struct misc_user_data misc; /* because it needs position information */
|
|
|
507 union magic_data magic;
|
|
|
508 struct magic_eval_data magic_eval;
|
|
428
|
509 } event;
|
|
|
510 };
|
|
|
511
|
|
440
|
512 DECLARE_LRECORD (event, Lisp_Event);
|
|
|
513 #define XEVENT(x) XRECORD (x, event, Lisp_Event)
|
|
428
|
514 #define XSETEVENT(x, p) XSETRECORD (x, p, event)
|
|
617
|
515 #define wrap_event(p) wrap_record (p, event)
|
|
428
|
516 #define EVENTP(x) RECORDP (x, event)
|
|
|
517 #define CHECK_EVENT(x) CHECK_RECORD (x, event)
|
|
|
518 #define CONCHECK_EVENT(x) CONCHECK_RECORD (x, event)
|
|
|
519
|
|
|
520 DECLARE_LRECORD (command_builder, struct command_builder);
|
|
|
521
|
|
|
522 #define EVENT_CHANNEL(a) ((a)->channel)
|
|
|
523 #define EVENT_TYPE(a) ((a)->event_type)
|
|
|
524 #define XEVENT_TYPE(a) (XEVENT (a)->event_type)
|
|
|
525 #define EVENT_NEXT(a) ((a)->next)
|
|
|
526 #define XEVENT_NEXT(e) (XEVENT (e)->next)
|
|
|
527 #define XSET_EVENT_NEXT(e, n) do { (XEVENT (e)->next = (n)); } while (0)
|
|
|
528
|
|
|
529 #define EVENT_CHAIN_LOOP(event, chain) \
|
|
|
530 for (event = chain; !NILP (event); event = XEVENT_NEXT (event))
|
|
|
531
|
|
|
532 #define EVENT_LIVE_P(a) (EVENT_TYPE (a) != dead_event)
|
|
|
533
|
|
771
|
534 #define CHECK_LIVE_EVENT(x) do { \
|
|
|
535 CHECK_EVENT (x); \
|
|
|
536 if (! EVENT_LIVE_P (XEVENT (x))) \
|
|
|
537 dead_wrong_type_argument (Qevent_live_p, (x)); \
|
|
428
|
538 } while (0)
|
|
771
|
539 #define CONCHECK_LIVE_EVENT(x) do { \
|
|
|
540 CONCHECK_EVENT (x); \
|
|
|
541 if (! EVENT_LIVE_P (XEVENT (x))) \
|
|
|
542 x = wrong_type_argument (Qevent_live_p, (x)); \
|
|
428
|
543 } while (0)
|
|
|
544
|
|
|
545
|
|
|
546 EXFUN (Fcharacter_to_event, 4);
|
|
|
547 EXFUN (Fdeallocate_event, 1);
|
|
|
548 EXFUN (Fevent_glyph_extent, 1);
|
|
|
549 EXFUN (Fevent_modeline_position, 1);
|
|
|
550 EXFUN (Fevent_over_modeline_p, 1);
|
|
|
551 EXFUN (Fevent_over_toolbar_p, 1);
|
|
|
552 EXFUN (Fevent_over_vertical_divider_p, 1);
|
|
|
553 EXFUN (Fevent_point, 1);
|
|
|
554 EXFUN (Fevent_window, 1);
|
|
|
555 EXFUN (Fmake_event, 2);
|
|
|
556
|
|
|
557 extern Lisp_Object QKbackspace, QKdelete, QKescape, QKlinefeed, QKreturn;
|
|
|
558 extern Lisp_Object QKspace, QKtab, Qmouse_event_p, Vcharacter_set_property;
|
|
|
559 extern Lisp_Object Qcancel_mode_internal;
|
|
444
|
560 extern Lisp_Object Vmodifier_keys_sticky_time;
|
|
428
|
561
|
|
502
|
562 /* The modifiers XEmacs knows about; these appear in key and button events. */
|
|
|
563
|
|
771
|
564 #define XEMACS_MOD_CONTROL (1<<0)
|
|
|
565 #define XEMACS_MOD_META (1<<1)
|
|
|
566 #define XEMACS_MOD_SUPER (1<<2)
|
|
|
567 #define XEMACS_MOD_HYPER (1<<3)
|
|
|
568 #define XEMACS_MOD_ALT (1<<4)
|
|
|
569 #define XEMACS_MOD_SHIFT (1<<5) /* not used for dual-case characters */
|
|
|
570 #define XEMACS_MOD_BUTTON1 (1<<6)
|
|
|
571 #define XEMACS_MOD_BUTTON2 (1<<7)
|
|
|
572 #define XEMACS_MOD_BUTTON3 (1<<8)
|
|
|
573 #define XEMACS_MOD_BUTTON4 (1<<9)
|
|
|
574 #define XEMACS_MOD_BUTTON5 (1<<10)
|
|
502
|
575
|
|
|
576 /* Note: under X Windows, XEMACS_MOD_ALT is generated by the Alt key
|
|
|
577 if there are both Alt and Meta keys. If there are no Meta keys,
|
|
|
578 then Alt generates XEMACS_MOD_META instead.
|
|
428
|
579 */
|
|
|
580
|
|
|
581 #ifdef emacs
|
|
|
582 /* Maybe this should be trickier */
|
|
|
583 #define KEYSYM(x) (intern (x))
|
|
|
584
|
|
|
585 /* from events.c */
|
|
440
|
586 void format_event_object (char *buf, Lisp_Event *e, int brief);
|
|
|
587 void character_to_event (Emchar c, Lisp_Event *event,
|
|
771
|
588 struct console *con,
|
|
|
589 int use_console_meta_flag,
|
|
|
590 int do_backspace_mapping);
|
|
440
|
591 void zero_event (Lisp_Event *e);
|
|
428
|
592 void deallocate_event_chain (Lisp_Object event);
|
|
|
593 Lisp_Object event_chain_tail (Lisp_Object event);
|
|
|
594 void enqueue_event (Lisp_Object event, Lisp_Object *head, Lisp_Object *tail);
|
|
|
595 Lisp_Object dequeue_event (Lisp_Object *head, Lisp_Object *tail);
|
|
|
596 void enqueue_event_chain (Lisp_Object event_chain, Lisp_Object *head,
|
|
771
|
597 Lisp_Object *tail);
|
|
428
|
598 int event_chain_count (Lisp_Object event_chain);
|
|
771
|
599 Lisp_Object transfer_event_chain_pointer (Lisp_Object pointer,
|
|
|
600 Lisp_Object old_chain,
|
|
|
601 Lisp_Object new_chain);
|
|
428
|
602 void nth_of_key_sequence_as_event (Lisp_Object seq, int n, Lisp_Object event);
|
|
|
603 Lisp_Object key_sequence_to_event_chain (Lisp_Object seq);
|
|
|
604 Lisp_Object event_chain_find_previous (Lisp_Object event_chain,
|
|
771
|
605 Lisp_Object event);
|
|
428
|
606 Lisp_Object event_chain_nth (Lisp_Object event_chain, int n);
|
|
|
607 Lisp_Object copy_event_chain (Lisp_Object event_chain);
|
|
|
608 /* True if this is a non-internal event
|
|
|
609 (keyboard press, menu, scrollbar, mouse button) */
|
|
|
610 int command_event_p (Lisp_Object event);
|
|
440
|
611 void define_self_inserting_symbol (Lisp_Object, Lisp_Object);
|
|
|
612 Emchar event_to_character (Lisp_Event *, int, int, int);
|
|
428
|
613 struct console *event_console_or_selected (Lisp_Object event);
|
|
|
614
|
|
|
615 /* from event-stream.c */
|
|
771
|
616 Lisp_Object allocate_command_builder (Lisp_Object console, int with_echo_buf);
|
|
428
|
617 void enqueue_magic_eval_event (void (*fun) (Lisp_Object), Lisp_Object object);
|
|
440
|
618 void event_stream_next_event (Lisp_Event *event);
|
|
|
619 void event_stream_handle_magic_event (Lisp_Event *event);
|
|
428
|
620 void event_stream_select_console (struct console *con);
|
|
|
621 void event_stream_unselect_console (struct console *con);
|
|
440
|
622 void event_stream_select_process (Lisp_Process *proc);
|
|
|
623 void event_stream_unselect_process (Lisp_Process *proc);
|
|
428
|
624 USID event_stream_create_stream_pair (void* inhandle, void* outhandle,
|
|
771
|
625 Lisp_Object* instream, Lisp_Object* outstream, int flags);
|
|
428
|
626 USID event_stream_delete_stream_pair (Lisp_Object instream, Lisp_Object outstream);
|
|
|
627 void event_stream_quit_p (void);
|
|
|
628
|
|
|
629 struct low_level_timeout
|
|
|
630 {
|
|
|
631 int id;
|
|
|
632 EMACS_TIME time;
|
|
|
633 struct low_level_timeout *next;
|
|
|
634 };
|
|
|
635
|
|
|
636 int add_low_level_timeout (struct low_level_timeout **timeout_list,
|
|
771
|
637 EMACS_TIME thyme);
|
|
428
|
638 void remove_low_level_timeout (struct low_level_timeout **timeout_list,
|
|
771
|
639 int id);
|
|
428
|
640 int get_low_level_timeout_interval (struct low_level_timeout *
|
|
771
|
641 timeout_list, EMACS_TIME *interval);
|
|
428
|
642 int pop_low_level_timeout (struct low_level_timeout **timeout_list,
|
|
771
|
643 EMACS_TIME *time_out);
|
|
428
|
644 int event_stream_generate_wakeup (unsigned int milliseconds,
|
|
771
|
645 unsigned int vanilliseconds,
|
|
|
646 Lisp_Object function,
|
|
|
647 Lisp_Object object,
|
|
|
648 int async_p);
|
|
593
|
649 int event_stream_resignal_wakeup (int interval_id, int async_p,
|
|
771
|
650 Lisp_Object *function, Lisp_Object *object);
|
|
428
|
651 void event_stream_disable_wakeup (int id, int async_p);
|
|
|
652
|
|
593
|
653 /* from signal.c */
|
|
|
654 int signal_add_async_interval_timeout (EMACS_TIME thyme);
|
|
|
655 void signal_remove_async_interval_timeout (int id);
|
|
428
|
656
|
|
|
657 /* from event-stream.c -- focus sanity */
|
|
|
658 extern int focus_follows_mouse;
|
|
|
659 void investigate_frame_change (void);
|
|
|
660
|
|
|
661 void emacs_handle_focus_change_preliminary (Lisp_Object frame_inp_and_dev);
|
|
|
662 void emacs_handle_focus_change_final (Lisp_Object frame_inp_and_dev);
|
|
|
663
|
|
|
664 Lisp_Object extract_this_command_keys_nth_mouse_event (int n);
|
|
|
665 Lisp_Object extract_vector_nth_mouse_event (Lisp_Object vector, int n);
|
|
|
666
|
|
|
667 void single_console_state (void);
|
|
|
668 void any_console_state (void);
|
|
|
669 int in_single_console_state (void);
|
|
|
670
|
|
|
671 extern int emacs_is_blocking;
|
|
|
672
|
|
|
673 extern volatile int sigint_happened;
|
|
|
674
|
|
|
675 #ifdef HAVE_UNIXOID_EVENT_LOOP
|
|
|
676 /* from event-unixoid.c */
|
|
|
677
|
|
|
678 /* Ceci n'est pas un pipe. */
|
|
|
679 extern int signal_event_pipe[];
|
|
|
680
|
|
|
681 void signal_fake_event (void);
|
|
|
682 void drain_signal_event_pipe (void);
|
|
|
683
|
|
|
684 extern int fake_event_occurred;
|
|
|
685
|
|
|
686 int event_stream_unixoid_select_console (struct console *con);
|
|
|
687 int event_stream_unixoid_unselect_console (struct console *con);
|
|
440
|
688 int event_stream_unixoid_select_process (Lisp_Process *proc);
|
|
|
689 int event_stream_unixoid_unselect_process (Lisp_Process *proc);
|
|
|
690 int read_event_from_tty_or_stream_desc (Lisp_Event *event,
|
|
771
|
691 struct console *con);
|
|
428
|
692 USID event_stream_unixoid_create_stream_pair (void* inhandle, void* outhandle,
|
|
771
|
693 Lisp_Object* instream,
|
|
|
694 Lisp_Object* outstream,
|
|
|
695 int flags);
|
|
428
|
696 USID event_stream_unixoid_delete_stream_pair (Lisp_Object instream,
|
|
771
|
697 Lisp_Object outstream);
|
|
428
|
698
|
|
|
699 /* Beware: this evil macro evaluates its arg many times */
|
|
|
700 #define FD_TO_USID(fd) ((fd)==0 ? (USID)999999 : ((fd)<0 ? USID_DONTHASH : (USID)(fd)))
|
|
|
701
|
|
|
702 #endif /* HAVE_UNIXOID_EVENT_LOOP */
|
|
|
703
|
|
|
704 /* Define this if you want the tty event stream to be used when the
|
|
|
705 first console is tty, even if HAVE_X_WINDOWS is defined */
|
|
|
706 /* #define DEBUG_TTY_EVENT_STREAM */
|
|
|
707
|
|
|
708 #endif /* emacs */
|
|
|
709
|
|
442
|
710 /* #### a hack, until accelerator shit is cleaned up */
|
|
|
711
|
|
|
712 /* This structure is what we use to encapsulate the state of a command sequence
|
|
|
713 being composed; key events are executed by adding themselves to the command
|
|
|
714 builder; if the command builder is then complete (does not still represent
|
|
|
715 a prefix key sequence) it executes the corresponding command.
|
|
|
716 */
|
|
|
717 struct command_builder
|
|
|
718 {
|
|
|
719 struct lcrecord_header header;
|
|
|
720 Lisp_Object console; /* back pointer to the console this command
|
|
771
|
721 builder is for */
|
|
|
722 #if 0
|
|
|
723 /* #### Not implemented: nil, or an event representing the first
|
|
|
724 event read after the last command completed. Threaded. */
|
|
442
|
725 Lisp_Object prefix_events;
|
|
771
|
726 #endif /* 0 */
|
|
|
727 /* nil, or an event chain representing the events in the current
|
|
|
728 keymap-lookup sequence. NOTE: All events in the chain MUST be
|
|
|
729 freshly allocated, with no pointers to them elsewhere. */
|
|
442
|
730 Lisp_Object current_events;
|
|
771
|
731 /* Last elt of current_events */
|
|
442
|
732 Lisp_Object most_current_event;
|
|
771
|
733 /* Last elt before function map code took over. What this means is:
|
|
442
|
734 All prefixes up to (but not including) this event have non-nil
|
|
|
735 bindings, but the prefix including this event has a nil binding.
|
|
|
736 Any events in the chain after this one were read solely because
|
|
|
737 we're part of a possible function key. If we end up with
|
|
|
738 something that's not part of a possible function key, we have to
|
|
|
739 unread all of those events. */
|
|
|
740 Lisp_Object last_non_munged_event;
|
|
|
741 /* One set of values for function-key-map, one for key-translation-map */
|
|
|
742 struct munging_key_translation
|
|
|
743 {
|
|
|
744 /* First event that can begin a possible function key sequence
|
|
|
745 (to be translated according to function-key-map). Normally
|
|
|
746 this is the first event in the chain. However, once we've
|
|
|
747 translated a sequence through function-key-map, this will point
|
|
|
748 to the first event after the translated sequence: we don't ever
|
|
|
749 want to translate any events twice through function-key-map, or
|
|
|
750 things could get really screwed up (e.g. if the user created a
|
|
|
751 translation loop). If this is nil, then the next-read event is
|
|
|
752 the first that can begin a function key sequence. */
|
|
|
753 Lisp_Object first_mungeable_event;
|
|
|
754 } munge_me[2];
|
|
|
755
|
|
665
|
756 Intbyte *echo_buf;
|
|
442
|
757 Bytecount echo_buf_length; /* size of echo_buf */
|
|
|
758 Bytecount echo_buf_index; /* index into echo_buf
|
|
771
|
759 * -1 before doing echoing for new cmd */
|
|
442
|
760 /* Self-insert-command is magic in that it doesn't always push an undo-
|
|
|
761 boundary: up to 20 consecutive self-inserts can happen before an undo-
|
|
|
762 boundary is pushed. This variable is that counter.
|
|
|
763 */
|
|
|
764 int self_insert_countdown;
|
|
|
765 };
|
|
|
766
|
|
440
|
767 #endif /* INCLUDED_events_h_ */
|
