Jamal,
Sure, that should work. But of course I'll add my normal disclaimer
that I have not actually tried this <smile>. But I see no reason this
wouldn't work. Of course when you are out of browse mode unregister the
hotkeys.
Doug
Jamal Mazrui wrote:
Doug,
So, if my script detects that browse mode is active, could it register
"Numpad-Down Arrow" and then in its event handler do
Keyboard.InsertKey vk_Down, 0
Jamal
On Wed, 9 Jul 2008,
Doug Geoffray wrote:
Date: Wed, 09 Jul 2008 13:41:36 -0400
From: Doug Geoffray <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Cursoring keys in browse mode
Jamal,
Yes, cursor keys are ignored in browse mode. Browse mode is Window-Eyes
and Window-Eyes knows internally how to navigate, etc. so this is all
built directly into Window-Eyes.
As for a script, yes, you could hook the numpad arrows and block them
but send a fake dedicated arrow.
Doug
Jamal Mazrui wrote:
So, in browse mode, are cursoring keys (defined in a set file) being
ignored, similar to how they are ignored in standard controls (besides
edit boxes)? In other words, if down arrow is defined as a cursoring key
to read the current line after the key is passed to the application, is
that being ignored in browse mode and custom functionality being provided
only to extended keys instead?
Is there currently a way via scripting that the Numpad keys could be
made to duplicate what the extended keys are doing in browse mode?
Jamal
On Wed,
9 Jul 2008, Michael D. Lawler wrote:
Date: Wed, 09 Jul 2008 13:13:55 -0400
From: Michael D. Lawler <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Cursoring keys in browse mode
Currently this isn't possible. Browse mode only pays attention to
the extended arrow keys.
At 02:12 PM 7/8/2008, you wrote:
I continue to work on a keyboard layout that seeks to provide a consistent
keyboard interface for JAWS users transitioning to Window-Eyes. Homer
Layout makes use of both scripting and TEXT2SET techniques to do this. I
am pleased with recent progress I have made after better understanding how
Window-Eyes resolves competing hotkey and cursoring key definitions, as
explained by Ron and Aaron.
A problem I am now trying to solve relates to browse mode. I notice that
in Internet Explorer, the extended cursoring keys read as expected, but
the Numpad ones produce no speech. Without browse mode on, they behave
the same, e.g., in EdSharp. I want Numpad keys to behave the same as
extended ones in IE as well. Unless the "Mouse mode" of this layout is
turned on, no hotkeys are defined for keys such as up arrow and down arrow
-- just cursoring keys in the active set file. Is there something else I
need to do in the set file or script?
Jamal
--
Michael D. Lawler
Voice 260-489-3671
Fax 260-489-2608
Internet mailto:[EMAIL PROTECTED]
web http://www.gwmicro.com
ftp ftp://ftp.gwmicro.com
GW Micro, Inc.,
Development Liaison and Technical Support Supervisor
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
