Yes, and we had to do deskchecking because computer time was so expensive.
I am about eight years behind you though.
Regards, Willem
On Sat, 13 Apr 2019, Didier Spaier wrote:
[The e-mail server of the sender could not be verified (SPF Record)]
Hello
Well, this discussion just reminds me how old I am as I
wrote a system specification for the first time 42 years ago...
Then things were going this way:
requirements > specification > development
Now things are going the other way round in many cases <smile>
No pun intended, sorry for the digression.
Best,
Didier
On 13/04/2019 21:44, Janina Sajka wrote:
Chuck's observation that one can continually press enter to keep
raising, or lowering levels sounds good enough to me. I think that's
sufficiently performant, so I am no longer thinking your design is at
all cumbersome. Color me convinced! <smile>
Janina
Willem van der Walt writes:
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@xxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
