On Thu, 17 May 2012, Dave Mielke wrote: > [quoted lines by Nicolas Pitre on 2012/05/17 at 14:08 -0400] > > >I think the only remaining issue appears to be the stuttering in menus. > > We could reduce its possibility by using a larger initial value and > increment. > Right now, it starts with 1, and increments to the exact length of each > longer > line as it encounters it. That was good for testing, and has also been > adequate > for braille, but is ultimately not very realistic. The only way to get the > right width for the menu pseudo-screen right up front would be to format all > possible values of all possible items at startup. That, to me, is way too > costly for such little gain.
I have no problem with the concept of starting with a line length of 1. What I don't understand is why the TTS is given that line, then stopped and given the same line again once the length is enlarged. Worse, the longer line is sent long after the truncated one, long enough that the synthesizer has time to start saying the first word. Why such a delay? My computer isn't that slow... I don't know how this is implemented, but surely the code can figure out that the line length is not sufficient for the new content, and enlarge it before speaking it? > Do you think that the concept of using the two arrows is intuitive enough? Yes, although I'd put the exit arrow at the left end e.g. "<--- Speech". > Do you think that the submenu names are good enough? I'd quickly chosen them > just to have something to work with, and am more than willing to change them. They are pretty good actually. The only suggestion I would make is: "Tables" --> "Braille Tables" Nicolas _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
