I don't think Window-Eyes has their own keyboard driver. JFW, does,
but that introduces a whole new kettle of fish.
At Tuesday 7/5/2011 04:08 PM, Sandra Fouts wrote:
I hate to ask this but do any other screen readers have this
problem. I thought that someone said that jaws does not have this
problem. Is that true? Just wondering.
-----Original Message-----
From: David [mailto:[email protected]]
Sent: Tuesday, July 05, 2011 4:05 PM
To: [email protected]; Michael D. Lawler
Subject: Re: mouse keys in we 7.5.1
Michael, and the rest of the staff,
I am not 100% sure, if I agree, when you say there is nothing you
can do about it. Wel,, at least not the way you said it.
First of all, I have tested quite a number of full-sized keyboards,
and never had any problem with them operating properly with WE.
Again, that is the full-sized ones. Now, then, what about the pure
numpads. From what you say, they might have a different set of
scancodes. Our local dealer told me, that even the same brand, would
work once, and not next time. Sounds a bit strange to me, since that
would indicate that the manufacturer randomly put in different
processors on their numpads, but same story never goes on the
full-sized keyboards. But OK, I am not a manufacturer, so have to
let that stand as it is.
Then, what about the way WE handles the kind of troublesome
keyboards? Is GW really all that out of luck? Yes, maybe the way
things stand today. Yet, it should be possible for you to make WE
capable of accepting other than the 'strict-standard' scancodes,
shouldn't it? That way, when the user runs into one of these
numpads, he could go to the hotkey manager in WE controlpanel, and
simply redefine his mousekeys to act upon the keystrokes from the
numpad. Seems the problem here is, that WE does not accept any
scancodes except from the narrow standard codeset.
I saw a similar case, when comes to the remote control for the computer.
Opening the Insert-1 feature of WE, and then hitting the
'next-track' and 'Previous-track' of the RC, did have no response at
all from WE. Again leading me to believe, that WE simply ignores any
scancode that would not happen to be in a rather strict standard
set. And, no, dont tell me the story about other software not acting
upon my RC, as it works perfectly in things like
Windows-media-player. Only WE does not 'see' tthe keystrokes from
the unit. I still think the same would be the case with the numpads
here in question. The solution would be, for GW to open up for WE to
see whatever scancodes comes from an input device, and thereby
letting the user have a chance of 'hooking on' to the actually sent
codes, from any input device. Thereby, he could even have used his
tiny RC for the computer as a mousepad. Or his gamepad (joystick),
which again WE refuses to 'see'.
Another question that raises itself here, is whether the numpads on
the market really come in all that many flavors. Have you, at GW,
looked into if there would happen to be a 'couple' of standards out
there? In such case, you could have opened up for WE to accept both
the number 1 standard, and the number 2 and 3 as well. Since other
software might accept things like joysticks and remote controls, and
WE does not, I still question the way WE handles the input codes.
Could be of interest here, to put out a question to the list
members, if any of you would happen to have tested one of the
troublesome keypads, with other software like Jaws or the like, and
tell us if it works with them - in case they have a more liberal
handling of scancodes.
At least, Michael, I find it a bit short-formed to simply claim
there is nothing you can do about it. Maybe not as WE stands at the
moment, but as I have pointed out, there should be chances that
there is a thing or two to be looked into. When things like WMP does
see my RC, and not WE, I do hold that WE is the problem - not the RC
itself. When a game on my PC, as well as things like the scripting
language of AutoHotKey sees my joystick, and WE does not; again I
hold that WE is narrow-minded. When a long number of numpads are not
recognized - and to me it seems by far the most of them - I do
question the way WE handles scancodes from input devices. GW might
likely be far more advanced than is the case with things like
AutoHotKey. When AHK manages a task, with little difficulty - and
you come and tell that your product does not, and there is simply
nothing you can do about it, I really find that a bit 'creeping out
under the fence'. So please, do back up your statement with
something a bit more waterproof. Why is there nothing to be done
about the problem? Why do some software see codes, and not Window-Eyes?
Thanks,
----- Original Message -----
From: "Michael D. Lawler" <[email protected]>
To: <[email protected]>
Sent: Tuesday, July 05, 2011 6:37 PM
Subject: Re: mouse keys in we 7.5.1
> The numpads are not sending the correct scan codes when the numlock is
> off. There isn't anything we can do about this. Any application that
> wants to use these keys will fail with these numpads.
>
>
>
> At 10:35 PM 7/2/2011, you wrote:
>>Seems you have run into a well-known bug in Window-Eyes. Don't ask me why,
>>but out of some reason, Window-Eyes does not recognize all kinds of USB
>>numpads. Strange, since the system does, or you would not have been able
>>to use the numpad in other applications. But again, Window-Eyes is PRETTY
>>fuzzy about that kind of stuff. Really something GW should have addressed,
>>as it has been a bug of WE for years.
>>
>>Best suggestion is, if possible, return your numpad, get a refund; and try
>>another one. If possible, bring your computer (if you have a laptop) with
>>you to the local computer store, and test the unit right there, before you
>>buy anything.
>>
>>And GW, ain't it time, to have Window-Eyes accept input devices that all
>>the flavors of Windows actually do accept, even without installing
>>anything but native drivers in Windows itself? Why all this fuzzy hazzle
>>about the numpads?
>>----- Original Message ----- From: "Rebecca Ilniski" <[email protected]>
>>To: <[email protected]>
>>Sent: Sunday, July 03, 2011 3:27 AM
>>Subject: mouse keys in we 7.5.1
>>
>>
>>>hi everyone. I have a windows 7 laptop and we 7.5.1. My laptop didn't
>>>have a numpad on it so I had to order one. I hooked it up but can't seem
>>>to use any of the mouse functioning keys. I tried to follow along with
>>>the thunderbird 2 podcast where the columns are set up in thunderbird
>>>but as I"m using the numpad none of the mouse keystrokes are not working.
>>>Are their any settings I need to enable? I know it's not the numpad as
>>>it does work in other applications.
>>>--
>>>Rebecca and Zeb
>>>email: [email protected]
>>>facebook: www.facebook.com/rebeccai5
>>>Zeb's page: www.facebook.com/zeb.ilniski
>>>If you reply to this message it will be delivered to the original sender
>>>only. If your reply would benefit others on the list and your message is
>>>related to GW Micro, then please consider sending your message to
>>>[email protected] so the entire list will receive it.
>>>
>>>GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
>>>manage your list subscription at http://www.gwmicro.com/listserv.
>>If you reply to this message it will be delivered to the original sender
>>only. If your reply would benefit others on the list and your message is
>>related to GW Micro, then please consider sending your message to
>>[email protected] so the entire list will receive it.
>>
>>GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
>>manage your list subscription at http://www.gwmicro.com/listserv.
>
> --
> 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
> If you reply to this message it will be delivered to the original sender
> only. If your reply would benefit others on the list and your message is
> related to GW Micro, then please consider sending your message to
> [email protected] so the entire list will receive it.
>
> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can
> manage your list subscription at http://www.gwmicro.com/listserv.
>
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and your
message is related to GW Micro, then please consider sending your
message to [email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You
can manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and your
message is related to GW Micro, then please consider sending your
message to [email protected] so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You
can manage your list subscription at http://www.gwmicro.com/listserv.
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
