The script basically works as follows. The API has an event called OnHotkey, which triggers each time the user invokes a hotkey action, regardless of what key is assigned to that action. The script hooks this event and also hooks an event that triggers every time a new window (or control, which is a child window) receives focus. If focus is on an edit or RichEdit type of control, then different behavior will happen for three hotkey actions (more could be added later if the technique seems viable): reading the current character, word, or line. If focus is in another type of control, or another hotkey is pressed, or the script cannot get a reference to the native object model of a RichEdit, then default reading from the OSM should occur instead.
Jamal On Fri, 26 Sep 2008, Raul A. Gallegos wrote: > Date: Fri, 26 Sep 2008 23:28:11 -0400 > From: Raul A. Gallegos <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: New Direct Text package > > Hello Jamal. So to make sure I understand what you are saying, if > Window-Eyes sees the character or word first, then your script works. > But if the osm is torked to the point that pressing the cursor or word > hot key is not even reading that, then the script us useless then? > > I just want to make sure because this script idea sounds good for buggy > osm issues in some areas such as Vista and a certain combination of > situations where edit boxes provide almost nothing but dinging when > arrowing through characters and pressing character or word hot keys > doesn't even work right. > > Jamal Mazrui said the following on 9/22/2008 12:55 PM: > > Hi Darrell, > > Yes -- as documented -- the script currently applies only to > > hotkeys that read the current character, word, or line in either an Edit > > or RichEdit control. Cursoring keys such as Backspace or Delete are not > > affected. I agree that would be a desirable enhancement, but technically > > it is more challenging. The reason is that the API lets a script inject > > itself into hotkey actions but not cursoring key actions at this time. > > > > Jamal > > On Mon, 22 Sep 2008, Darrell > > Shandrow wrote: > > > >> Date: Mon, 22 Sep 2008 05:46:35 -0700 > >> From: Darrell Shandrow <[EMAIL PROTECTED]> > >> Reply-To: [email protected] > >> To: [email protected] > >> Subject: Re: New Direct Text package > >> > >> Hello again Jamal, > >> > >> Hmm. Do I understand correctly that this script may not apply to use of > >> keys > >> like backspace and delete? Perhaps, that's my issue here... :-) If this is > >> the case, you may want to consider making this clear in the script's > >> documentation. > >> > >> > >> ----- Original Message ----- > >> From: "Darrell Shandrow" <[EMAIL PROTECTED]> > >> To: <[email protected]> > >> Sent: Monday, September 22, 2008 5:41 AM > >> Subject: Re: New Direct Text package > >> > >> > >> Hello Jamal, > >> > >> In which editing situations is this script supposed to work? I'm writing a > >> message in Outlook Express right now, and several OSM related editing > >> problems I've previously reported still exist. Does it just not yet work in > >> this particular editing control? The potential for this script is quite > >> exciting, indeed, as editing problems associated with the OSM are annoying > >> to say the least. > >> > >> > >> > >> > >> ----- Original Message ----- > >> From: "Jamal Mazrui" <[EMAIL PROTECTED]> > >> To: <[email protected]> > >> Sent: Monday, September 22, 2008 5:32 AM > >> Subject: New Direct Text package > >> > >> > >> Direct Text 1.0 > >> > >> When focus is in an Edit or RichEdit control, this script causes the > >> Window-Eyes hotkeys for reading the cursor character, word, or line to > >> obtain text directly from the control rather than from the off screen > >> model. To toggle off this direct reading, press Alt-Insert-D. Note that > >> cursor keys that read text after navigation will still use the off screen > >> model. > >> > >> This global script requires GW Toolkit. > >> > >> > >> Jamal > >> > > > -- > Raul A. Gallegos -- GW Micro Technical Support > Voice: 260-489-3671 -- Fax: 260-489-2608 > WEB: http://www.gwmicro.com >
