Suggestion: UI keyword in subjects.

[Lukas]

What about (some brainstorm in the morning):
* adding ~0.9s time frame between the moment user enters radial area and
actual sound level change In those 0.9s click would be simply ignored (mouse
wheel, of course, would work as usual). This way accidental click should be
prevented
* displaying volume level in the centre of wheel, while hovering "active"
area, so giving additional feedback what wil happen if you click here
* allow at most 20-25% increase of sound level per click thus preventing
accidental 20 to 100% increases (leaving lowering sound level without limits
- it can't explode you eardrums)

As for slider on hover approach, its also option, but when creating hover
effect of size 100*20px over 80*80px element, it either creates blinking -
you hover over top corner or square, it transforms to rectangle and area
below becomes inactive, so it goes back to square. And the loop is started,
since its on hover, not on click; Its solvable by adding transparent
100*80px element below, but its kind a  hackish solution, I personally
always try to avoid.
Also, as You have mentioned, more mouse movement would be required

Have a nice day,
Lukas

On 5 August 2010 02:16, Thomas Pfeiffer <colomar at autistici.org> wrote:

>
> This approach could work as well. However it really would be important to
> get
> the contrast right. Plus we'd have to make sure that users won't
> accidentally
> turn the volume up as at least some seem to be doing now.
> That would be an advantage of displaying a slider next to the icon on
> hover:
> The user would have to move the cursor over it to change the volume so
> accidental changes would be prevented. On the other hand, your suggestion
> would require less mouse movement to change the volume. So it's basically
> safety vs. efficiency here.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/amarok-devel/attachments/20100805/3e1a2b27/attachment.htm