Button lost event

They are not really lost, they are aborted in these cases:

• When the user holds the button down for over qx.event.handler.GestureCore.LONGTAP_TIME (500) because at that point the gesture emulation fires a “longtap” instead of a “tap” event. The “longtap” is what you get  on a touch device when pressing and holding. Wisej emulates the same on desktop devices to be able to have the same code. You can increase the time setting: “qx.event.handler.GestureCore.LONGTAP_TIME = 1000” in a javascript call.
• When the use presses down, move the mouse a bit (like many irritating users do 🙂 and then release. The javascript framework cancels the “tap” in that case. The distances are different for devices: qx.event.handler.GestureCore.TAP_MAX_DISTANCE : {“touch”: 40, “mouse”: 5, “pen”: 20}. You can increase it like this in a js call “qx.event.handler.GestureCore.TAP_MAX_DISTANCE.mouse = 10”.

It’s all here:

https://github.com/iceteagroup/wisej-qx/blob/master/event/handler/GestureCore.js

We had the “lost clicks” report many times and are looking at removing the TAP_MAX_DISTANCE check, but it’s tricky because it’s also used on mobile when the user touches, drags and releases and changes this deep in can have unintended consequences.