Re: tracking down NVDA triggers
toggle quoted messageShow quoted text
Actually, for this one, I think John’s advice is a bit better – I myself have experienced it on my ThinkPad, and it appears to be an event-related problem. To truly find out what’s up, you need to run NVDA in debug mode (restart NVDA with debug logging enabled) and capture the log output (it’ll print all sorts of things). Only after trying to figure out what’s up with NVDA should we look into SFC.
From: firstname.lastname@example.org <email@example.com> On Behalf Of Brian Vogel
On Tue, Oct 1, 2019 at 12:33 PM, John Isige wrote:
No, it isn't. I cannot help if you cannot be bothered to read, and comprehend, the advice given. You might want to think about that before spouting off garbage like this again.
Brian - Windows 10 Pro, 64-Bit, Version 1903, Build 18362
The color of truth is grey.
~ André Gide