> When one register double-click callback for a HOLD browser and make
> a double click on a line in it, THREE callbacks are invoked:
>
> 1. Normal (single-click) callback for the browser
> 2. Double-click callback
> 3. Normal (single-click) callback - AGAIN.
>
> Well, this is something quite undesirable on most occasions.
> Is this meant to be so, or a bug?
I dunno if it's a bug or a feature but it is confusing, isn't it?
The problem is, of course, that what action XForms should take is
ambiguous at the first click -- should it eat the click and wait for
the second click or pass it on. The second single click callback is
probably extraneous but, who knows, maybe some application would want
to receive it.
I believe I suggested a possible workaround for this annoyance a few
weeks ago.
Check the archives.
spl
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/