Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
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.
I don't generate timer events. Only client messages with the offix protocol
atom.
> 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?
Yep... I'll try...
By the way (perhaps someone has an idea): the crash occurs only AFTER the drop
(i.e. I can see that the text gets inserted, and then XEmacs crashes). Perhaps
it has something to do with the evaluation of the misc-user event?
Regards,
Oliver.