You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Comment 1 by mdcurran on 2010-02-13 10:07
I assume this was a problem even before the rewrite today?
In Windows 7 I do get layout changes.
But in Vista and XP I don't remember getting them.
I think simply the reason is that in these Operating Systems, getMessage / callwndproc hooks are never fired for console windows as it seems you can not inject in to these windows at all.
At this point in time I can't think of how to fix it, with out coming up with another way of detecting the change in general.
Also, how ever we do do it, it still must be in-process as getKeyboardLayoutName does not take a thread identifier, it only works on the current thread.
Perhaps there is a way to ask the console for its current keyboard layout, via the console API functions. If so, then we probably could just check if it changes on each key press in keyboardHandler.
Comment 2 by nvdakor on 2014-07-25 13:23
Hi,
I can confirm that NVDA does announce keyboard language/layout changes in Windows 8.x while using command prompt.
Thanks.
Reported by aleksey_s on 2010-02-13 08:34
steps to reproduce
current results
NVDA doesn't report the change to keyboard layout
expected results
NVDA must gracefully report the change
The text was updated successfully, but these errors were encountered: