On Wed, Mar 31, 2021 at 03:05 PM, Vinod Benjamin wrote:
Wow! i am Able to find the addon doing the issue. Need to write to the developer .-
Wonderful. Thank you very much for taking the time to read the tutorial and then following through with all the steps.
I'm not trying to insult add-on developers in any way, but it's generally been the case that add-ons break something rather than the NVDA core. Part of that is the way the development cycles of the NVDA core and NVDA add-ons diverge. Many NVDA Add-On developers do this entirely on their own time and as time is available and sometimes changes in NVDA core requires add-on changes, and sometimes not.
Debugging software and determining root causes is a slow process that requires attention to detail.
Again, thanks very much for actually carrying out the necessary process to isolate your issue to its source.
Brian - Windows 10 Pro, 64-Bit, Version 20H2, Build 19042
Always remember others may hate you but those who hate you don't win unless you hate them. And then you destroy yourself.
~ Richard M. Nixon