|
Re: running beta of nvda
Tyler Spivey
Maybe the solution here is to open issues for every single error we hear
toggle quoted messageShow quoted text
that isn't a duplicate of something else, since these are obviously important enough to get the user's attention. You (and others who are part of the project) don't seem to understand that the sound is useless to most of us. It comes up so often that it's just background noise. Let's take some simple examples: 1. Restart with add-ons disabled, press control NVDA v, tab twice, hit escape, press control NVDA s to switch synth then hit enter. You'll most likely get: RuntimeError: wrapped C/C++ object of type BoxSizer has been deleted Does this matter to anyone? Probably not, since it's been there for a while. Next one. Switch to a synth which is an addon, then restart with add-ons disabled. You hear the startup sound, then the error sound. When you look, you find out that it's just NVDA not being able to load the synth, because addons are disabled, which is a completely expected case. But this shouldn't produce the sound. There are others, which come up when doing seemingly simple tasks. Alt tabbing just now is a perfect example of something I would not expect to fail: Could not register for UIA events for element Why is that important? If it can't register because of a COM Error, it should do something else, or tell you if you debug. Alt tabbing again, we get another error sound, this time for an unreachable wave player.
On 9/28/2020 11:32 AM, Joseph Lee wrote:
Hi,
|
|
|
|
Re: running beta of nvda
On Mon, Sep 28, 2020 at 02:59 PM, Joseph Lee wrote:
As for making debug tones optional or suppressing it in beta releases, it should be something that must be taken care of from alpha channel first i.e. let’s ask NV Access via GitHub.- Works for me. But the production of error tones when there are no errors is, quite simply, a philosophical no-go for me. I don't care if some "benchmark tone" is used, but it should never be what would indicate an error condition under normal circumstances. And I really, really hope that the tone used is not hard-coded and could be "swapped out" during beta, and swapped back in for release, if there are "spare debug tones" that use error tones during beta. Ideally, those spare tones should use their own sound. -- Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041 It’s hard waking up and realizing it’s not always black and white. ~ Kelley Boorn
|
|
|
|
Re: running beta of nvda
Hi, One counterexample, although not that intuitive, is desktop watermark shown on Windows Insider Preview builds; they are early beta quality builds so folks expect stability when considering small details. As for changing the debug tone, this will involve changes at the source code, code branch, and deployment level:
Another consideration is communicating errors that developers can catch – not only we get reports from users and try our best to reproduce certain issues, folks use tones as means of debugging and locating errors (whenever we hear a debug tone, we developers would open the NVDA log and read recent tracebacks). This is important as it then allows developers to either fix the issue right away or discuss strategies to do so in the future. For people relying on debug tones for debugging issues, it gives us an early warning so major bugs will not slip to stable releases – this is why when contributors file issues and pull request, if a beta cycle is active and a bug was discovered with a beta build, they are directed to send changes based on latest beta branch commit. At the moment beta branch is in a “suspended animation” – translators are committing localization updates, and unless critical issues are discovered, the next release from beta channel will be 2020.3 release candidate. As for making debug tones optional or suppressing it in beta releases, it should be something that must be taken care of from alpha channel first i.e. let’s ask NV Access via GitHub. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Monday, September 28, 2020 11:43 AM To: nvda@nvda.groups.io Subject: Re: [nvda] running beta of nvda
On Mon, Sep 28, 2020 at 02:32 PM, Joseph Lee wrote:
- Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041 It’s hard waking up and realizing it’s not always black and white. ~ Kelley Boorn
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
Ralf Kefferpuetz
NVDA-X would break my fingers on my left hand, lol. Seriously I think it is free….
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Oleksandr Gryshchenko
Sent: Montag, 28. September 2020 19:33 To: nvda@nvda.groups.io Subject: Re: [nvda] Introducing the Quick Dictionary add-on #addonRelease
Guys, can we use NVDA+X ?
|
|
|
|
Re: running beta of nvda
On Mon, Sep 28, 2020 at 02:32 PM, Joseph Lee wrote:
This behavior is intentional – beta is not really a stable build yet, so NVDA developers are interested in fixing major errors if possible, hence the debug tone.- But, Joseph, if one is not experiencing major errors, and I am not, and this darned tone is being presented, that, in and of itself, is a bug. I've had it come up repeatedly when absolutely nothing I can detect is amiss. I'm glad to hear I'm not the only one, and I'm happy to jump on to the, "this should not be occurring" bandwagon. You don't intentionally produce spurious indicators, ever. -- Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041 It’s hard waking up and realizing it’s not always black and white. ~ Kelley Boorn
|
|
|
|
Re: running beta of nvda
Hi, This behavior is intentional – beta is not really a stable build yet, so NVDA developers are interested in fixing major errors if possible, hence the debug tone. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Don H
Sent: Monday, September 28, 2020 11:20 AM To: nvda@nvda.groups.io Subject: Re: [nvda] running beta of nvda
Yep running beta 2 of NVDA On 9/28/2020 9:35 AM, Chris via groups.io wrote:
|
|
|
|
Re: running beta of nvda
Don H
Yep running beta 2 of NVDA
On 9/28/2020 9:35 AM, Chris via
groups.io wrote:
|
|
|
|
Re: Veracryp's SecureDesktop opt not usable latest trunk
Roger Stewart
You can't use NVDA on the secure screen if it is portable--only an installed copy can do this.
toggle quoted messageShow quoted text
Roger
On 9/28/2020 11:57 AM, john doe wrote:
Hello all,
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
Oleksandr Gryshchenko
Guys, can we use NVDA+X ?
It seems to me that it will be quite convenient. Thank you very much for your advice!
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
Ralf Kefferpuetz
Control-alt-D
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rob Hudson Sent: Montag, 28. September 2020 17:33 To: nvda@nvda.groups.io Subject: Re: [nvda] Introducing the Quick Dictionary add-on #addonRelease Oh, so it is lol. I was going to suggest control+NVDA+d but that gets you document formatting. Then I guess NVDA+Shift+E will work. Or NVDA+Y. ----- Original Message ----- From: "Oleksandr Gryshchenko" <kita.zup+groups@gmail.com> To: nvda@nvda.groups.io Date: Mon, 28 Sep 2020 08:29:13 -0700 Subject: Re: [nvda] Introducing the Quick Dictionary add-on #addonRelease No, Rob, it is "Audio mute modes"...
|
|
|
|
A more intelligent NVDA OCR?
Luke Robinett
First of all, just having OCR capabilities in NVDA has been a game changer! It was only recently that I learned you can hit enter on text in the OCR window and NVDA would try to invoke that corresponding control in the application.
With that in mind, it seems like this could be evolved even further. Is the technology available such that NVDA could try to not only recognize text from the app but ascertain the structure of the user interface, perhaps organizing things into form elements like buttons, text fields etc and then presenting them in the same element browser we use for web pages? Barring that, perhaps a more immediately reachable upgrade would be different actions we can take on items in the OCR result. For example, instead of just the option to hit enter to invoke something, what about a Context menu that lets you invoke it or simply position the mouse cursor where that element was found? I’m not a python developer so take these as suggestions from a layman, but if possible, I think it would frankly revolutionize NVDA. I Work with a lot of music recording/production software and much of it is completely inaccessible, relying on highly visual interfaces that screen readers have no handle into. Something like what I’ve described would really be amazing for these types of programs. Thanks!
|
|
|
|
Veracryp's SecureDesktop opt not usable latest trunk
john doe
Hello all,
I'm playing with veracrypt's CLI, (1). when using the '/secureDesktop' option to mount an encrypted file, NVDA is totaly lost in the secure desktop password prompt with the latest trunk release ofNVDA in portable mode. Command to trigger the issue: VeraCrypt-x64.exe /v x.vc /l o /q /secureDesktop It would be awsome if that could be addressed. For follow-up, please CC me as I'm not subscribed to the list. 1) https://www.veracrypt.fr/code/VeraCrypt/plain/doc/html/Command%20Line%20Usage.html?id=4a7ed6926b276cf88c2485ea2a5e95b7f91e4ac1 -- John Doe
|
|
|
|
Re: waterfox issues still not solved
How do you get it to do this in chrome or brave?
toggle quoted messageShow quoted text
The only thing I get is an alert stating there is a download, I then have to hit controlj then choose keep or discard. This would be mainly for executables or microsoft installer packages the rest I don't mind if it saves including audio.
On 28/09/2020 9:23 pm, Gene wrote:
You can make the dialog pop up in your face with Firefox or Chrome or Brave. I have it pop up so that I can rename the file if I wish or change the download location, though I choose one place for all downloads, then don't change it.
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
Rob Hudson
Oh, so it is lol.
toggle quoted messageShow quoted text
I was going to suggest control+NVDA+d but that gets you document formatting. Then I guess NVDA+Shift+E will work. Or NVDA+Y.
----- Original Message -----
From: "Oleksandr Gryshchenko" <kita.zup+groups@gmail.com> To: nvda@nvda.groups.io Date: Mon, 28 Sep 2020 08:29:13 -0700 Subject: Re: [nvda] Introducing the Quick Dictionary add-on #addonRelease No, Rob, it is "Audio mute modes"...
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
Oleksandr Gryshchenko
No, Rob, it is "Audio mute modes"...
Oh, how difficult it is to choose a free keyboard shortcut... Ok, please advise me the right combination. Thank you! ;)
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
Rob Hudson
NVDA+shift+d would work.
toggle quoted messageShow quoted text
----- Original Message -----
From: "abdul muhamin" <abdulmuhamin600@gmail.com> To: "nvda@nvda.groups.io" <nvda@nvda.groups.io> Date: Mon, 28 Sep 2020 19:43:33 +0500 Subject: Re: [nvda] Introducing the Quick Dictionary add-on #addonRelease Yes, but this key is conflicting with the emoticons addon
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
abdul muhamin
toggle quoted messageShow quoted text
From: Oleksandr Gryshchenko
Sent: Monday, September 28, 2020 7:21 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Introducing the Quick Dictionary add-on #addonRelease
Hi all :)
|
|
|
|
Re: running beta of nvda
Chris
Are you sure you are running the beta and not the alpha?
From: Don H
Sent: 28 September 2020 14:34 To: nvda@nvda.groups.io Subject: [nvda] running beta of nvda
Running the latest beta of NVDA on a Win 10 computer. Getting the error ding every time I go to a web page with Google Chrome. Also get a error ding when I close Google Chrome.
|
|
|
|
Re: Pronunciation: Unwanted Dates
Jonathan,
Then try one of these for the replacement string, depending on how you want or don't want the leading zero on the track number announced zero four Mary oh four Mary four Mary Brian -- Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041 It’s hard waking up and realizing it’s not always black and white. ~ Kelley Boorn
|
|
|
|
Re: Introducing the Quick Dictionary add-on
#addonrelease
Oleksandr Gryshchenko
Hi all :)
Supanut Leepaisomboon wrote: > I think one solution to the NVDA+d hotkey conflict is to leave the hotkey to activate the addon Yes, I have already fixed this error. The add-on now uses NVDA + E. Good luck to all!
|
|
|
