[elisa] [Bug 417223] Use of go-next-view-page icon is confusing

[Matthieu Gallien]

https://bugs.kde.org/show_bug.cgi?id=417223

--- Comment #7 from Matthieu Gallien <matthieu_gallien at yahoo.fr> ---
(In reply to Nate Graham from comment #4)
> I proposed that about a year ago. Lollypop implements it this way, with
> single-click being used to enter an item.
> 
> IIRC the objection back then was that enter-on-single-click would make it
> difficult or impossible to select an item, which makes the inline buttons
> appear. This is not a huge deal for pointing device users since they also
> appear on hover, but for touch users, selecting an item is the only way to
> make the inline buttons appear.
> 
> However maybe we could accept that touch users would need to enter an item
> and use the play now/enqueue button from the toolbar rather than using the
> hover buttons.
> 
> Thoughts, Matthieu?

The touchscreen of my laptop is broken. I can no longer test or work on that.
It is sad but I plan to keep this laptop as long as I can. I will see if I can
get some alternative device to work on that.

Anyway, I believe that the InputHandler may allow to fine tune the interaction
depending on the device used to interact.

In the meantime, we would need to have somebody actively involved to test and
work on that. If this is not possible, we should avoid blocking progress and
work on mouse interaction primarily.

About your specific question, I believe that this is an acceptable deal because
the inner view should be fast to appear and provides the needed controls.

I have a last question, should we not try to follow the single/double click KDE
wide setting ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.