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
