When enabling finger dragging on the Viewport class via setScrollOnDragEnabled, the dragging process can be interrupted when the user touches the screen with a second finger.
It all boils down to this line in juce_Viewport.cpp:
if (Desktop::getInstance().getNumDraggingMouseSources() == 1 && ! doesMouseEventComponentBlockViewportDrag (e.eventComponent))
I see what you did here (avoid having multiple fingers dragging the same viewport), but I think that rather than checking if the number of mouse sources is 1, the code should check that the dragging source is the one that actually started the dragging on the Viewport. The current code causes the interruption of the drag not only for the linked Viewport, but also for other Viewports where a second finger is added.
I bet (haven’t really tried it though) that if you add two instances of ListBox in the same Component, the user isn’t currently able to drag them both at the same time, using two separate fingers.
So, on to the fix: what about having a member pointer to the MouseInputSource that started the dragging? At mouseDown, if the pointer is invalid, you take it from the incoming MouseEvent reference, then you use it to do the checking at mouseDrags and finally, if that’s the one being removed, you reset it to nullptr at mouseUp.
There’s also a problem with the inertia. Recently @SQUARESEQUENCE posted a workaround which addresses both issues:
The other issue is that swiping pages with GUI elements does not work as one would expect. If one begins a swipe movement over a button, one expects to swipe the viewport, not click the button. So one needs a considerable amount of custom code to get things to work properly and things get tricky when it comes to comboboxes, sliders, a viewport inside the viewport, etc.
I think an update of the Viewport which fixes these issues and adds a swiping mode which behaves as in iOS and Android would be a very reasonable feature request!
Thanks for your patience. I’ve put together a fix for the initial issue (secondary touches interrupting Viewport scrolling), but we’re currently only merging very high-priority bugfixes to develop so that we can put out a bugfix release in a week or so. The fix for this issue will probably land on develop shortly after this bugfix release.
