From: Takashi Iwai <tiwai@suse.de>
To: Kirill Marinushkin <k.marinushkin@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC, alsa-utils] RFC: alsamixer: Improve description of playback switches
Date: Mon, 26 Mar 2018 09:38:41 +0200 [thread overview]
Message-ID: <s5ho9jb70ce.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180326051144.16672-1-k.marinushkin@gmail.com>
On Mon, 26 Mar 2018 07:11:44 +0200,
Kirill Marinushkin wrote:
>
> Currently, all playback switches are described as mute. It is shown as:
>
> [OO] == sound is on (left and right channels)
> [MM] == sound is muted (left and right channels)
>
> But cards can have different kinds of switch controls, not only mute. At
> least usb-audio provides boolean controls as playback switches for:
>
> * clock source validity (read only switch)
> * processing features on/off (rw switch)
> * potentially other similar use-cases
>
> It becames confusing, because it is shown as:
>
> [OO] == clock source is valid
> [MM] == clock source is invalid
>
> [OO] == processing feature is on
> [MM] == processing feature is off
>
> And from the help, it is not clear how to toggle such switches.
>
> In this RFC, I suggest to show switches more generic:
>
> [yy] == sound on / clock source is valid / processing feature is on
> [nn] == sound muted / clock source is invalid / processing feature is off
I don't think it's better solution, sorry. The current symbol isn't
the best of the best, I admit. But yy/nn isn't better from the
visibility POV, and what's worse is the sudden change of user
experience on such a long-living application. Also, you can't expect
every user understanding English.
If the problem is about the mismatch of mute/non-mute symbol against
the switch state, we may blacklist / whitelist the element names.
At easiest, we can keep using mute symbol for "xxx Playback Switch".
This is very likely a mute control. The rest is neutral, so something
more generic symbol can be used for on/off instead of 'M'.
thanks,
Takashi
next prev parent reply other threads:[~2018-03-26 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 5:11 [RFC, alsa-utils] RFC: alsamixer: Improve description of playback switches Kirill Marinushkin
2018-03-26 7:38 ` Takashi Iwai [this message]
2018-03-26 18:32 ` Kirill Marinushkin
2018-03-26 20:41 ` Andrew Chant
2018-03-26 21:13 ` Kirill Marinushkin
2018-03-26 21:44 ` Takashi Sakamoto
2018-03-26 21:53 ` Kirill Marinushkin
2018-03-27 19:12 ` Kirill Marinushkin
2018-03-26 8:19 ` Takashi Sakamoto
2018-03-26 18:37 ` Kirill Marinushkin
2018-03-26 18:42 ` Kirill Marinushkin
2018-03-26 22:03 ` Takashi Sakamoto
2018-03-26 22:22 ` Kirill Marinushkin
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=s5ho9jb70ce.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=k.marinushkin@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.