drag + zoom in LensWindowManager

Daniel Blaukopf daniel.blaukopf at oracle.com
Fri Aug 8 15:40:34 UTC 2014

Hi Johan,

1. You are correct that it is Monocle that is being maintained, not Lens. So it would be better to get a fix in there.
2. There is an automated test framework for bugs like this in tests/system/src/test/java/com/sun/glass/ui/monocle. If you open a JIRA there then we’ll try to add a test for this case. This tests can still be run on Lens as well (for now).
3. Do you mean we get a TOUCH_PRESSED event when two fingers are already on the screen and one is moved?


On Aug 8, 2014, at 4:04 PM, Johan Vos <johan at lodgon.com> wrote:

> I have an issue with zoom gestures on Android.
> My UI listens for drag events to drag a node, and we also listen to zoom
> events to zoom.
> Zoom gestures are generated by dragging 2 fingers on the touch screen.
> When the user pushes the second finger on the touch screen, for initiating
> the zoom gesture, a drag event is generated.
> In LensWindowManager.c a call to lens_wm_notifyMultiTouchEvent is made, and
> the primaryPointIndex is passed. When the first finger is pushed, the index
> is 0 and when the second finger is pushed, the index is 1.
> This is twice detected as a TOUCH_PRESSED event. The first event will cause
> the onDraggingAction to be set to true, and the second event is then
> considered a DragEvent.
> There are a number of ways to fix this, but I'm wondering if it is still
> worth doing this (or rather jump to monocle right now)...
> Does anyone circumvented this on other platforms?
> - Johan

More information about the openjfx-dev mailing list