From: "Glenn At Home" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: : Using enter or using arrows, that is the question
Date: Sat, 13 Apr 2019 14:33:08 -0500 [thread overview]
Message-ID: <CEB15F1366A24761A35005EDABE71B5D@NUCPPYH> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1904131717050.5275@willempc.meraka.csir.co.za>
Hi Willem,
Any chance you can do this for ARM as well?
Thanks.
----- Original Message -----
From: "Willem van der Walt" <wvdwalt@csir.co.za>
Cc: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Sent: Saturday, April 13, 2019 10:35 AM
Subject: Re: : Using enter or using arrows, that is the question
Hi all,
Janina, thanks for the suggestion, but no, I am writing this in python,
alsamixer is written in C as far as I know.
It is just the way I have written the code which kind of precludes the
up/down arrow thing, and that I do not really see what is so wrong with
the current way things are done.
What I might consider doing, would be to replace the two options, one for
up and one for down, with one option, e.g.
Playback volume 30 percent
I can then make it use two other keys, e.g. pageup and pagedown or f2 and
f3 to go softer or louder.
I am not that keen on doing it, as it deviates from the way things are
selected and used throughout the rest of the program.
The up/down arrows are already used to move among the options.
Left and right arrows would be the obvious choice, but I am using speakup
and it will say space if I use them.
One can also make the keys configurable later.
One needs the percentages when e.g. trying to get a silent soundcard
going, and if I take it out there, how would you know at what levels the
controls are?
Hope this make sens.
Willem
On Sat, 13 Apr 2019, Janina Sajka wrote:
> Hmmm, I hadn't considered that simply repeated presses of enter would
> continue to adjust levels in realtime. That just might be good enough,
> imo.
>
> RE: How to put such behavior on the up/down keys, alsamixer is likely
> the source to copy from.
>
> Janina
>
> Chuck Hallenbeck writes:
>>
>> Hi all,
>>
>> I prefer to remain witgh the use of enter to make adjustments in
>> controls suchaas Master, for instance, which makes a lot of sense given
>> that upward adjustment and downward adjustment are offered as separate
>> items in the menu for that control. Arrowing to the upward item and
>> pressing enter makes the adjustment and leaves the control selected,
>> so that pressing enter repeatedly makes a series of adjustments in
>> the same direction. It's beautiful to see the percent figure change and
>> hear the perceived loudness change in sync with the numeric value. I'm
>> not sure how one would put the entire job of making adjustment onto
>> the arrow keys.
>>
>> Just my $0.02 worth.
>>
>> Chuck
>>
>>
>>
>>
>> --
>> Here In Northeast Ohio, The Moon is Waxing Gibbous (57% of Full)
>> If you don't stand for something, you will fall for anything.
>> Sent from Lucille's missing iPhone.
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
> --
>
> Janina Sajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup: http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
>
>
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Janina Sajka
` Willem van der Walt
` Glenn At Home [this message]
` Willem van der Walt
` Janina Sajka
` Didier Spaier
` Willem van der Walt
` Gregory Nowak
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=CEB15F1366A24761A35005EDABE71B5D@NUCPPYH \
--to=glennervin@cableone.net \
--cc=speakup@linux-speakup.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).