[prev in list] [next in list] [prev in thread] [next in thread]
List: amarok-devel
Subject: Re: Suggestion: UI keyword in subjects.
From: Lukas <1lukas1 () gmail ! com>
Date: 2010-08-05 9:13:16
Message-ID: AANLkTing=JzarYe6s3rYFi4cbLOXYS6KsGsyv5ZjijP9 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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@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.
[Attachment #5 (text/html)]
What about (some brainstorm in the morning):<br>* 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 <br>
* displaying volume level in the centre of wheel, while hovering "active" \
area, so giving additional feedback what wil happen if you click here<br>* 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)<br>
<br>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. <br>
Also, as You have mentioned, more mouse movement would be required<br><br>Have a nice \
day,<br>Lukas<br><br><div class="gmail_quote">On 5 August 2010 02:16, Thomas Pfeiffer \
<span dir="ltr"><<a \
href="mailto:colomar@autistici.org">colomar@autistici.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); \
margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br> </div>This \
approach could work as well. However it really would be important to get<br> the \
contrast right. Plus we'd have to make sure that users won't accidentally<br> \
turn the volume up as at least some seem to be doing now.<br> That would be an \
advantage of displaying a slider next to the icon on hover:<br> The user would have \
to move the cursor over it to change the volume so<br> accidental changes would be \
prevented. On the other hand, your suggestion<br> would require less mouse movement \
to change the volume. So it's basically<br> safety vs. efficiency \
here.</blockquote></div><br>
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic