I wrote:
If I don't actually double click on the node, the problem disappears. If I
call the DblCLick() sub from e.g. a NodeClick() event or a button Click()
it works fine.
And so it went away.
The workaround--I'm big on workarounds, having a past as a web designer--is
to not do important stuff in the DblClick() event. What I do now is this:
In the DblClick() event I set a property, eventWrapper, to the code I want
to execute. Nothing else. A timer triggers 50 times a second, looking at
the eventWrapper property. If it's nonempty, the timer evals the string. Voila!
The timer doesn't seem to affect performance, and the delay between double
click and action isn't noticable unless you know it's there.
It's not industrial-strength tested yet, but it seems to work fine.
- - - - -
There is a new release with this workaround and a few extra bug fixes and
features like e.g. "@ISA modules" (an inheritance tree). The new binary
will open in a DOS console so error messages aren't lost. Maybe that
explain why the binary doesn't work for some of you.
- - - - -
If you think I spam this list with too many messages about this one
application, please let me know and I'll cut back. Just let me know when I
get annoying :)
/J
--
Johan Lindström, Sourcerer, Boss Casinos Ltd, Antigua
[EMAIL PROTECTED]
