toggle quoted messageShow quoted text
You are right, I'm going to call this a "feature". We were aware of this behaviour. From memory, I think it is one of those things that looks simple to fix, but would actually be very complex.
The main risk is that if you turn numlock on and use the numpad insert as the NVDA modifier, then you won't be able to exit input help until you turn numlock off again.
On Fri, Nov 18, 2016 at 3:36 PM, Jacob Kruger <jacob@...>
Not a bug report or anything, but, just a warning since it seems slightly odd, and, took me roundabout 2 seconds to realise what had happened...<smile>
Was double-checking layout of numpad keys for something else, so turned on NVDA's input help using NVDA key + number row 1.
Anyway, ran through all the numpad keys, including hitting just the numlock key, and, it did still turn on numlock, which meant that suddenly all the numpad keys were reporting their number characters, along with stating that numlock was being included - numlock numpad 5, for example.
Anyway, all this meant was that to then turn off input help, I first had to press numlock key by itself again, before then using the original keystroke of NVDA + number row 1, since otherwise it just reported numlock numpad 0, followed by 1 to me, but, kept input help turned on.
And, if relevant, this is on my windows 10, anniversary upgrade, 64 bit machine, and, running NVDA 2016.3, with full desktop keyboard layout.
"Resistance is futile, but, acceptance is versatile..."
Training Material Developer