Hi Chuck, If this is more of a problem with how a programmmer codes their particular editor as opposed to how speakup reads cursor movements, then I'll relent and say 1.0. Is there a particuar factor anyway that would make speakup speak cursor movements in one editing enviornment, and not another? Greg On Fri, Sep 28, 2001 at 06:35:09AM -0400, Charles Hallenbeck wrote: > Hi Greg > > On Thu, 27 Sep 2001, Gregory Nowak wrote: > > > Give me an example of a DOS screenreader > > like that in an editor. > > I can't help you on that one, but here is an interesting observation: > > I am a pine user, and so I am relatively comfortable with pico editor. > Pico tracks the cursor perfectly but it does not spontaneously read > anything when the cursor moves. On the other hand, the pico look-alike > 'nano' which also tracks the cursor perfectly, does spontaneously read > each character as you move the cursor left or right. > > The point is: Cursor tracking is not the problem. The problem is what gets > spoken as the cursor is tracked, and on that score there3 are wide > variations from one application to the next in a Linux environment. > > I do not think it is helpful to look for DOS parallels. > > Chuck > > > > Visit me at http://www.mhonline.net/~chuckh > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759. > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup
