At 12:06 AM 8/15/2001, you wrote:
>Leston Drake wrote/ schreef:
>
> > Does anyone know how to turn this off (without setting ListBehavior to
> false)?
> > Or ideas for trapping the second one?
>flushEvents() ?
Good idea, Sjoerd.
I tried flushEvents() without success.
Here's what I ended up with as a workaround:
on mouseDown
# you have to give it a delay, in order to allow the second mouseDown to
be sent, so it can be killed
send "myMouseDown" to me in 2 ticks
end mouseDown
on myMouseDown
put "myMouseDown message received at"&&the long seconds
# wait so you can see what's in the command window change
wait for 0.5 seconds
killExtraMessage
end myMouseDown
on killExtraMessage
if ",myMouseDown," is in the pendingMessages then cancel item 1 of the
pendingMessages
else put "no extra message"
end killExtraMessage
Obviously this is a quick and dirty workaround (I'm assuming there is only
1 pending message here), but it does demonstrate an effective way to kill
the 2nd mouseDown, which you can see because you don't get a 2nd
"myMouseDown received at..." in the Command Window.
To reiterate, you get 2 mouseDown messages when you click on a field with
the following properties:
1) ListBehavior = True
2) TraversalOn = False
3) field's text <> empty
Change any one of these 3 and you don't get the 2nd mouseDown message.
BTW, I'm using MC 2.3.2 on Windows ME.
Does anyone else get this behavior? I'm very curious to know if it happens
on other platforms, etc.
> > TIA,
> > Leston
>Good luck,
>Sjoerd
>
>
>Archives: http://www.mail-archive.com/[email protected]/
>Info: http://www.xworlds.com/metacard/mailinglist.htm
>Please send bug reports to <[EMAIL PROTECTED]>, not this list.
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
