I do not know how to accomplish the following cursoring key actions through straightforward scripting techniques: Speak Window, Word Enhanced, Office Attribute Status, and Office Smart Tab -- documentation excerpts below. I think the ability to perform cursoring key actions should be added to the API, though understand why it is not a priority now.
Regards, Jamal Speak Window - When being set, prompts you to select a window number 0-49; when responding to a keystroke, speaks the selected window. Word Enhanced - Reads all consecutive punctuation in a word (or group of characters) if the cursor is on a punctuation mark or reads all consecutive text if the cursor is not on a punctuation mark. This is useful for applications that consider punctuation as a separate word. Office Attribute Status - Reads attributes such as Bold, Italic, Underline, Font Size, and Show All. By default, CTRL-B, CTRL-I, CTRL-U, and CTRL-SHIFT-* are set up to read Bold, Italic, Underline, and Show All respectively in the Microsoft Word set files. Office Smart Tab - The characteristic of this cursoring key will change depending upon the context of the cursor. For example, if the cursor is inside a form in Microsoft Word, then the Office Smart Tab cursoring key will speak the current control. If the cursor is inside a table in Microsoft Word, then the Office Smart Tab cursoring key will speak the new current cell contents. If the cursor is inside the main document in Microsoft Word, then the Office Smart Tab cursoring key will speak the cursor position. On Thu, 21 Aug 2008, Doug Geoffray wrote: > Date: Thu, 21 Aug 2008 08:53:37 -0400 > From: Doug Geoffray <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: Cursoring key actions > > Jamal, > > Most of the things you can do other ways as I'm sure you are aware. > Some things don't make sense to just execute. For example, prior > character before and character before can't just be executed because it > has to get the character before the cursoring key is sent to the > application and then spoken after the application does its thing. > Again, you can simulate this yourself but it doesn't make sense to just > execute this functionality by a single method call. Word Enhanced isn't > available but could be simulated. The office options are also not > available but could be called directly into the Word object model to do > what they do and in fact, a lot more. So really we are just talking the > two you pointed out as not giving direct access to. We may add these at > some point but the good news is there is a workaround in the mean time. > > Doug > > Jamal Mazrui wrote: > > I know a script can perform hotkey actions with the ExecuteHotkey method. > > Is there a way to perform cursoring key actions as well? Hotkey actions > > provide equivalent functionality for many of the cursoring key actions > > available in a set file definition, but there appear to also be some where > > there is no equivalent. For example, can script code perform the word > > enhanced action or the Office smart tag one? > > > > Jamal > > > > > > -- > Doug Geoffray > GW Micro, Inc. > Voice 260-489-3671 > Fax 260-489-2608 > http://www.gwmicro.com >
