Oliver Graf <ograf(a)fga.de> writes:
It only happens for drags from within XEmacs to the same instance of
XEmacs. Drags from other apps/XEmacsens do not produce the problem.
But why does it crash in the timer code? Somehow it thinks it gets an
unexpected timer event.
Perhaps I can solve it the following way: I test if the window is one
of this
XEmacs, and if this is true, the drag handler does not send an event to
itself, but directly creates the misc-user-event.
This is ugly. Wouldn't it be better to try find the real cause?
Jan