-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/108686/
-----------------------------------------------------------
(Updated Jan. 31, 2013, 8:06 p.m.)
Review request for Amarok and KDE Usability.
Changes
-------
Explain it in more detail.
Description (updated)
-------
Some of the actions in context menu are shown only when the Shift key is
pressed. We were wondering, if this were okay at all, and if yes, which hint
would be better.
To explain a bit more:
in Amarok 2.5, the context menu (of a track, album etc.) used to have all the
options (among others):
* Copy to Collection ->
* Move to Collection ->
* Move to Trash
* Delete
With goal to (a) make accidental data-loss (or unwanted effect) harder for
novice users (b) make the context menu simpler, a fancy "hold Shift to swich to
move/dangerous operations" behaviour was implemented:
- without Shift held:
* Copy to Collection -> [with "Press Shift key for ..." tooltip]
* Move to Trash [with "Press Shift key for ..." tooltip]
- with Shift key held (updated itself immediately after pressing the key):
* Move to Collection ->
* Delete
However, we discovered that discoverability (hehe) is really a problem when
even experienced long-term Amarok users didn't know about the way to trigger
Move/Delete. What would be the best approach here?
Diffs
-----
Diff: http://git.reviewboard.kde.org/r/108686/diff/
Testing
-------
File Attachments
----------------
http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hidden_actions.png
http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hint_1.png
http://git.reviewboard.kde.org/media/uploaded/files/2013/01/31/hint_2.png
Thanks,
Edward Hades Toroshchin
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel
