https://bugs.kde.org/show_bug.cgi?id=419651
--- Comment #6 from Ariadne Conill <aria...@dereferenced.org> --- Regarding going against the platform: I think single-click activation makes sense for navigational tasks, but it doesn't make sense for other tasks. For example, not only is this a problem in Audacious, but two different friends who use Amarok also said they find the single-click behaviour annoying there, since clicking on a song makes it play immediately when single-click mode is enabled. In an audio player, a common pattern is to select a bunch of tracks and enqueue them to a separate playlist or play queue. With the single-click behaviour, doing this is quite counter-intuitive. So, in Audacious, we attach a QProxyStyle to our subclassed audqt::TreeView widgets that suppresses the single-click activation for those widgets. I think, therefore, what makes most sense is to have a flag on the widgets that provides a hint as to what the purpose of the widget is. That seems to also be in line with how Qt provides other hints. Then you either hint the widgets where single-click activation is useful (like navigation), or you hint the widgets where single-click activation is counter-intuitive (like playlists). For something like a playlist, the single-click activation pattern doesn't make much sense, doesn't match any other popular platform (Audacious does target Mac, Windows, etc too), but as previously stated does seem useful for navigation. So, that is what I propose doing. -- You are receiving this mail because: You are watching all bug changes.
