Well, what I have been thinking about is the assignment of any key defined to be a cursoring key. A cursoring key is defined to be a key which is used by your speech software and then is passed on to the application and also used by the application. Now there may be many things which you want a cursoring key to do. For instance, your left arrow key generally would execute a function character after which voices the character where the caret is after the application has finished processing. Whereas the backspace key generally would voice the prior character before which means the character to the left of the caret, before the key is given to the application. There are about 10 or so of these and what I have been thinking about is allowing -- internal to speakup -- the assignment of keys to such functions. Keymaps are no good for this, because things need to be on a per console basis (unless local keymaps are part of the new 2.5 stuff?). I guess you see where I am going with this. on Wednesday 04/30/2003 Shaikh, Saqib(sshaik at essex.ac.uk) wrote > Purely out of interest, what do you mean by: > > > Now all we need is the Vocalize type functionality and an internal key > translation > > and we are there! > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- John Covici covici at ccs.covici.com
