Colin Rafferty <craffert(a)ms.com> writes:
2 x_event_to_emacs_event(0x7ffb70d8, 0x0, 0x0, 0x7ffb6e08, 0x0,
0x7ffb6d54, 0x0, 0x7ffb6cfc)
["/ms/user/c/craffert/build/xemacs/xemacs-21.0-b46/src/event-Xt.c":1151,
0x10162f24]
Sorry, forgot the patch... here it is.
Output should look like this:
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 227 _DND_PROTOCOL
-> is a dnd message
received ClientMessage: 208 DndProtocol
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
received ClientMessage: 223 WM_PROTOCOLS
the 223 messages are enters, and inbetween is a drop from OffiX files (note
that the two messages results from compability to version 0 of the OffiX
protocol).
Please try this on your machine.
Regards,
Oliver.
--- event-Xt.c.orig Fri Jul 3 14:25:09 1998
+++ event-Xt.c Fri Jul 3 14:30:46 1998
@@ -1111,6 +1111,10 @@
explicitly prohibits. */
XClientMessageEvent *ev = &x_event->xclient;
#ifdef HAVE_OFFIX_DND
+ stderr_out ("received ClientMessage: %u %s\n",
+ x_event->xclient.message_type,
+ XGetAtomName(x_event->xclient.display,
+ x_event->xclient.message_type));
if (DndIsDropMessage(x_event))
{
unsigned int state, modifiers = 0, button=0;
@@ -1120,6 +1124,8 @@
Lisp_Object l_type = Qnil, l_data = Qnil;
Lisp_Object l_dndlist = Qnil, l_item = Qnil;
struct gcpro gcpro1, gcpro2, gcpro3, gcpro4;
+
+ stderr_out (" -> is a dnd message\n");
GCPRO4 (l_type, l_data, l_dndlist, l_item);