From: Clemens Ladisch <clemens@ladisch.de>
To: Kusanagi Kouichi <slash@ac.auone-net.jp>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] alsamixer: Confirm that a drastic volume change is intentional.
Date: Fri, 13 Jan 2012 13:31:03 +0100 [thread overview]
Message-ID: <4F102407.60708@ladisch.de> (raw)
In-Reply-To: <20120113111449.EDBE06FC039@msa105.auone-net.jp>
Kusanagi Kouichi wrote:
> Home key has been disabled because it might at least surprise a user
> unless volume is already nearly full. Not only home but 9, 8 and so
> on might also surprise a user.
The surprise is not so much the amount of the resulting volume but the
meaning of the key; the user might have assumed that Home jumps to the
first control. If the volume is too loud after pressing 9, it's easy
to press another smaller digit, but it would be more difficult to
remember a volume change key if the jump to 100% happens in a situation
where a volume change wasn't expected at all.
(And this would be a good reason to disable the End key, too.)
> So instead of disableing key, show confirmation dialog for drastic
> volume change.
A confirmation dialog is annoying to users who know what they're doing,
and still confusing to anybody else.
Instead of having commands that require confirmation, I think it's
better to have only commands whose meaning is obvious.
In this case, the jump-to-100% command doesn't seem to be very
worthwhile because you could just as well press PageUp a few times.
Is there a reason that you need this command, other than for symmetry
with the End command?
Regards,
Clemens
next prev parent reply other threads:[~2012-01-13 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 11:14 [PATCH] alsamixer: Confirm that a drastic volume change is intentional Kusanagi Kouichi
2012-01-13 12:31 ` Clemens Ladisch [this message]
2012-01-14 12:35 ` Kusanagi Kouichi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F102407.60708@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=slash@ac.auone-net.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).