Re: Reading command prompt


Felix G.
 

Hello again,
turns out my theory was wrong. The exact explanation can be found in
https://github.com/nvaccess/nvda/issues/513
There were two commits which actually fixed this for anything above Vista, but they caused other problems so were reverted.
Maybe it would make sense to experiment with the STABILIZE_DELAY timer in the Winconsole class.
Kind regards,
Felix

Felix G. <constantlyvariable@...> schrieb am So., 4. Sep. 2016 um 09:57 Uhr:

Hi,
my theory is that it has to do with the keyboard hook. Technically, it seems that characters printed to the console are seen by the keyboard hook as key input, and then treated as such. To whoever wrote that hook: could this be true? I mean, could console output erroneously make your hook trigger?
Kind regards,
Felix

Pranav Lal <pranav.lal@...> schrieb am So., 4. Sep. 2016 um 04:13 Uhr:
Tyler,

The problem with turning of character echo is that when I work on the commandline, I like to hear the characters I type so we still need a real fix for this problem.

Pranav

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Tyler Spivey
Sent: Sunday, September 04, 2016 6:01 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Reading command prompt

This is normal.
To fix it, turn off character and word echo.
On 9/3/2016 5:27 PM, Supanut Leepaisomboon wrote:
> Hi all,
>
> When I tried the new NVDA 2016.3RC2, I noticed that NVDA still spell
> out the output of the command prompt, for example when I launch it it
> would spell out the current directory in full; this issue occurred on
> Windows
> 10 and is quite annoying when using the command prompt.
>
> Is this a bug in NVDA? If so will this gets fix?
>
>







Join nvda@nvda.groups.io to automatically receive all group messages.