At 11:57 2002-05-17 +0200, Guillem Cunillera Wefers wrote:
I only use the NodeClick, and it seems to go wrigth, but:
- Some NodeClick events are send when I haven't done, for instance when I
roll the wheel
Maybe this is related to the problems I had, I don't know. This is how I
"solved" my problem:
-----
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.
-----
/J
-------- ------ ---- --- -- -- -- - - - - -
Johan Lindström Sourcerer @ Boss Casinos [EMAIL PROTECTED]
Latest bookmark: "HowStuffWorks - Learn how Everything Works!"
http://www.howstuffworks.com/
