[DASH] diagonal swipe is recognized as a scroll

[Oren Horev]

#98 on all devices

Current behaviour
-------------------------
Horizontal swipes in the dash are often performed with an angular aspect away form the horizontal axis. Angular swipes that have an angular component (more than +/- 30 deg) are often recognised as scrolls which can seem mistaken by the user having th intention of swiping.

Excepted behaviour
---------------------------
recognise the horizontal intention in swipes regardless of the angular component by evaluating ratio between horizontal /vertical speeds or distances not just angle

------ UX Comment ------

We are working on the redesign of the dash/scopes navegation, therefore this bug is not valid anymore. It'd be a waste of engineering time and effort since with Qt and qml list component there is not much we can do about that. Basically there is a horizontal list (dash and scopes) and vertical list (scope content) and we need to interpret if user is trying to do horizontal or vertical swipe and lock to that until finger released.

We'll publish an update on the new dash design as soon as it's available.

[Andrea Cimitan (cimi)]

I'll try...

[Daniel d'Andrada (dandrader)]

Let me have a shot at it...

[Daniel d'Andrada (dandrader)]

>Excepted behaviour
>---------------------------
>recognise the horizontal intention in swipes regardless of the angular component by evaluating ratio >between horizontal /vertical speeds or distances not just angle

Too vague for a specification and even contradictory in a sense.

The ratio between horizontal and vertical distances (or speeds) translates into an angle and vice-versa.

Need more info on the expected behavior.

But I guess that what the reporter means is that a vertical scrolling can be aborted and turned into a horizontal dash-switch if the original vertical movement turned into a drastic horizontal one. And vice-versa. Because the current logic is that once a tendency (horizontal/vertical) has been identified early in the gesture, the UI movement is locked in that direction. So in practice what the reporter wants seems to be removing that direction lock. I.e. that it can be unlocked if there's a sustained, dramatic, direction change.

[Daniel d'Andrada (dandrader)]

I noticed that while a list is scrolling by itself (e.g. after a fast vertical flick) you cannot successfully perform a horizontal flick (there will be no dash switch). You have to first stop the list movement and then perform the horizontal flick. Is that considered a bug and, if so, is that included in this one?

[Daniel d'Andrada (dandrader)]

I don't know, as long as you don't try a horizontal flick while a dash list is still moving, it works fine for me.

Need details on what's expected.

[Albert Astals Cid (aacid)]

This has been incomplete for months so i'll close it as invalid

[Vesa Rautiainen (vesar)]

In the new design scopes will be taken away from the dash and will act as apps in the system and in many parts of the navigation. So dash won't exist in the future as a horizontal list anymore. This will fix this usability issue and I wouldn't put any efforts at this point to fix this.