[Loadstone] Unassigned keys.
shawn at loadstone-gps.com
Sun May 11 09:25:22 BST 2008
The screen reader shouldn't read the screen unless something happens that
causes it to change. When an unused key is pressed loadstone just ignores
it causing no screen changes. Talks does the right thing and doesn't say
anything. If mobilespeak takes this as a reason to read the screen there's
nothing we can do about that.
The fact that talks says "talks" everytime the talks key is pressed is kind
of annoying and not a behaviour I'd want to duplicate.
On Sun, 11 May 2008, Ari Moisio wrote:
> Usually i do not consider it as a bug if the screenreaders read the
> screen content.
> At least Talks users should not be annoyed because Talks announces
> 'talks' every time the edit key is pressed. Probably 'shift' is not more
> annoying than result of previous function for MS users either.
> You can still escape from the Gates of hell: Use Linux!
> mr. M01510
> On Sun, 11 May 2008, Shawn Kirkpatrick wrote:
>> That sounds like a mobilespeak bug. When a key is not assigned loadstone
>> doesn't do anything to the screen. Mobilespeak just seems to have some bugs
>> there's no work around for.
>> The shift speaking thing could be done but would probably get very annoying
>> very quickly.
>> On Sun, 11 May 2008, Ari Moisio wrote:
>>> One little wish for unassigned key behavior: it would help at least the
>>> beginners if unassigned key will clear the message buffer. Currently
>>> unassigned key will repeat the result of previous command.
>>> Same problem with the shift key, it also repeats previous result with
>>> It would also help newcomers if the shift key is announced by printing
>>> 'shift' in the screen.
>>> You can still escape from the Gates of hell: Use Linux!
>>> mr. M01510
>>> Loadstone mailing list
>>> Loadstone at loadstone-gps.com
>> Loadstone mailing list
>> Loadstone at loadstone-gps.com
> Loadstone mailing list
> Loadstone at loadstone-gps.com
More information about the Loadstone