Double click should be treated as two single clicks about ipe HOT 5 CLOSED

Have you tried mapping 129 to 1 in INKTOOL:mouseButton?

Qt already reports two events for a double-click: The first one is a normal mouse click, the second one is reported as a double-click. By mapping this back to a normal click it should work (unless Qt does something else?)

from ipe.

I tried to map 129 to 1 in MODEL:mouseButtonAction() and it works. It does
not work by mapping 129 to 1 in INKTOOL:mouseButton. The reason is that the
MODEL:mouseButtonAction() function will block 129. So actually, I think 129
is not used any where in the Ipe program. Therefore it is probably safe to
map 129 to 1 inside MODEL:MouseButtonAction(). It is also a good design if
double clicks are not used at all.

My point here is that this may also need to be corrected in Ipe in the
released official version. The reason is that when writing using Inktool,
and writing quickly (at normal writing speed), the second stroke in two
consecutive strokes is reported (correctly) by Qt as a double click, but
Ipe should really accept 129 the second click as a normal click. I cannot
see any side effect of doing this, inside INKTOOL at least.

On Tue, Aug 4, 2015 at 3:19 AM, otfried [email protected] wrote:

Have you tried mapping 129 to 1 in INKTOOL:mouseButton?

Qt already reports two events for a double-click: The first one is a
normal mouse click, the second one is reported as a double-click. By
mapping this back to a normal click it should work (unless Qt does
something else?)

—
Reply to this email directly or view it on GitHub
#3 (comment).

from ipe.

There are Ipe users that insist on having double-clicks as an alternative to the right mouse button, because their tablet pen does not have a right button. Double-clicks can be used to terminate paths, for instance.

So yes, 129 is used in some tools (see tools.lua and search for 0x81).

So I cannot simply get rid of the double-click events, and instead Ipe needs to handle them. It seems mapping it to 1 in MODEL:mouseButtonAction should be enough.

from ipe.

And yes, I've already included this in the official version for the next release.

from ipe.

Thanks.

from ipe.