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. It's a shame that the
callback function cannot access the event that called it.
But, as you concluded, there is no easy way to solve this. Coding the
event in the dnd data is a solution as good as any other.
Is the loop reference evil? It seems to work fine...
Loop reference is OK; our GC is perfectly capable of handling it.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
By any chance, have you seen a summoned 9th order fire elemental
wandering around? No? Oh.. Tell me if you do.