The GW-Scripting list is a discussion list for information regarding the development and use of Window-Eyes scripts. Any subscriber of the GW-Scripting list has the ability to post on-topic messages.
From:
Chip OrangeSubject:
a scripting issue with intercepting cursoring keysDate:
Sat, Apr 3, 2010 4:35:19 pmHi GW and anyone else,
I was hoping for some opinions as to what is causing my scripting problem in
the MS Word script. it's that I intercept all scripting keys with
onCursorKey and return true, insert some extra speech sometimes, then use
the .execute method of the key so that the WE speech that resulted from this
keypress will occur. the only reason I'm doing it this way is so I can
sometimes insert my extra speech before WE gets to speak (just like my wife
does!)
Anyway, this works fine for all cursoring keys except the backspace key.
what happens there, even when my script doesn't add any speech, is that
backspace no longer speaks the character you've just spaced over.
I've worked around it by specifically testing for the backspace and
excluding it from those I intercept, but I'd like to understand what's
happening with backspace, so it doesn't bite me again with some other key.
Is this just a matter of timing, and the very slight delay I introduce by
intercepting the key with onCursorKey and then executing it later?
thanks.
Chip
I was hoping for some opinions as to what is causing my scripting problem in
the MS Word script. it's that I intercept all scripting keys with
onCursorKey and return true, insert some extra speech sometimes, then use
the .execute method of the key so that the WE speech that resulted from this
keypress will occur. the only reason I'm doing it this way is so I can
sometimes insert my extra speech before WE gets to speak (just like my wife
does!)
Anyway, this works fine for all cursoring keys except the backspace key.
what happens there, even when my script doesn't add any speech, is that
backspace no longer speaks the character you've just spaced over.
I've worked around it by specifically testing for the backspace and
excluding it from those I intercept, but I'd like to understand what's
happening with backspace, so it doesn't bite me again with some other key.
Is this just a matter of timing, and the very slight delay I introduce by
intercepting the key with onCursorKey and then executing it later?
thanks.
Chip


