Bug 219026 - Amarok is un-usable (or hard to use) without mouse
Summary: Amarok is un-usable (or hard to use) without mouse
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.3-GIT
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Amarok Bugs
URL:
Keywords:
: 86729 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-12-17 08:27 UTC by La Wezen
Modified: 2014-08-14 09:45 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 2.5
Sentry Crash Report:
myriam: Usability+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description La Wezen 2009-12-17 08:27:18 UTC
Version:           2.2.1 (using 4.3.4 (KDE 4.3.4) "release 2", KDE:43 / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.5-0.1-desktop

Amarok kayboard usability is lost since previous version for KDE 3.5
1) Unable to collapse or expand Artist in the Local Music browser
2) Unable to navigate via views (playlist, music browser and etc.)
3) Unable to search in playlist and music browser (search in old version is very usable)
4) Unable to switch music sources
5) ...
this list may be expanded by any user with the unplugged mouse.

Please, make Amarok more comfortable to use with keyboard.
Comment 1 Myriam Schweingruber 2009-12-17 12:30:59 UTC
We optimized Amarok for the use with either a mouse or a touchscreen. Basic keyboard shorcuts are already available.
Comment 2 La Wezen 2009-12-24 12:59:56 UTC
This is good! 
But mouse or touchscreen optimization should not broke keyboard functionality.
Comment 3 Hans Wurst 2009-12-24 13:03:02 UTC
*** This bug has been confirmed by popular vote. ***
Comment 4 Hans Wurst 2009-12-24 13:05:35 UTC
For instance, expanding Artist in the Local Music browser is too hard by mouse and unable by keyboard. This is really bad.
Comment 5 Myriam Schweingruber 2009-12-25 09:19:35 UTC
Setting usability flag.
Comment 6 Kevin Funk 2010-05-28 16:24:01 UTC
*** Bug 86729 has been marked as a duplicate of this bug. ***
Comment 7 Victor Yang 2010-10-31 04:38:05 UTC
A particular feature I miss from amarok version 1.x is the behavior of cursor key navigation of the local collection. I'm currently using amarok 2.3.0.

For example, in the Media Sources panel, I browse Local Music and have Merged View (button near top-right of Local Music listing) turned off, and sorting by Artist/Album.

Up, down and right arrows work as expected -- they move up/down one item, and right expands an item.

However the left arrow behavior is very annoying. If the current highlighted item is an album or artist that has been expanded, the item will be closed *and* the cursor/highlight will jump to the parent of the item just closed. That means if you close the artist's expanded view, the cursor jumps all the way to the beginning of your collection! If an album was closed, the cursor jumps to the artist, skipping any and all albums that were between the just-closed album and the artist level.

The problem is partially improved with Merged View turned on: when closing an artist, the cursor does not jump to the beginning of the collection; however, closing an album still automatically jumps up to the artist level.

Expected/desired behavior:
For an expanded artist or album, left arrow should close the item, and the cursor should remain on the just-closed item. On an already closed/collapsed artist or album, left arrow should jump to the parent item. This is the behavior in Dolphin with Expandable Folders turned on.
Comment 8 vedant agarwala 2013-06-09 08:57:41 UTC
Is this bug still valid?
My observation:
The left button doesn't produce any undesirable results. When left key is hit on any item (generally song) that cannot be expanded (or contracted) it does nothing, and if the item can be contracted, it does so.

Expected behavior IMO:
When left key is hit on a single item (i.e. not a group that can be expanded or contracted) the cursor should move to the top of the group without closing the group.
Comment 9 Myriam Schweingruber 2014-08-14 09:45:46 UTC
This has long been fixed...