Hrvoje Niksic <hniksic(a)srce.hr> writes:
> Oliver Graf <ograf(a)fga.de> writes:
>
> > I think I have a solution. Do you think that this is evil:
> > - when I create the misc-user-event object (the dnd-data), I cons a reverence
> > to the event itself into it. So the function still has access to
> > it's event.
> [...]
>
> Not evil. A bit /ad hoc/ maybe, but not evil. Now I at least
> understand what you are referring to, and I think that it is a
> fundamental flaw in the misc-user-event model.
OK, I just thought of a way to fix it: how about adding a
`current-misc-user-event' variable that will be set to the event
immediately prior to dispatching the callback function? This is still
sort of a kludge, but less so than hardcoding the event to dnd-data by
the C code.
What do you think? Ben, what do you think of this solution?
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Jone's law: The man who smiles when things go wrong has thought of
someone to blame it on.