|
Re: NVDA Curiosity
YYeah same here, the only issue I am having is the espeak squisher issue and its not uber bad like I want to chuck the computer into hell and buy jaws, its just a slight accent squish that I think they will get fixed its probably something wrong with the phonem data than anything else since thats what it sounds like.
toggle quoted messageShow quoted text
On 4/06/2016 6:29 a.m., Roger Stewart wrote:
I'm having no problems with the newest nvda and I use Firefox and
|
|
|
|
Arlene
The latest version of NVDA Rocks! When you are reading e-mails, it tells or announces gramme0072 errors. This rocks!
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Andre Fisher Sent: June-03-16 6:19 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Meet NVDA 2016.2, bringing spelling error beep, grammar error detection and more to your work, home and everything in between #NVAccess #Release I agree with Bhavya. That's a better route in the long run, rather than reverting to an older version of NVDA, which does not provide the best functionality. I would also like more persons to test out NVDA, even the snapshots or RCs, just to ensure that more bugs are fixed. On 6/3/16, Bhavya shah <bhavya.shah125@gmail.com> wrote: Hi Nasrin,
|
|
|
|
Re: NVDA Curiosity
Arlene
No, You can't put the start sound that xp used at start up. I like the
toggle quoted messageShow quoted text
sound start up for windows 7. Does ten have that same sound at start up like you would in 7?
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ron Canazzi Sent: June-03-16 12:57 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA Curiosity Hi Carlos, Yes, you are right. For sentimental reason, I kept an old XP SP3 system--mostly for storage and because I finagled a way to play some DOS games on it through the command line structure. But just this past week, the old faithful gave up the ghost: some sort of motherboard issue as well as a shaky hard drive. So I decided to replace it with a reconditioned Windows 7 Home Premium system for about $125 plus tax. I am used to having tons of back-ups in the event of a calamity so I am comfortable with 3 computers: my 2 Windows 8 systems (one to be upgraded shortly to ten or when I get the nerve) and the old XP system, now to be replaced with the Windows 7 reconditioned box. Oh for the tragedy of not hearing that old XP boot sound! I know you can configure the new system with the old sounds--but just like dating a blonde you really liked and then when she dumps you dating another blonde; it's really not quite the same <laugh>! ...And so it goes. On 6/3/2016 2:49 PM, Carlos wrote: Hello:-- They Ask Me If I'm Happy; I say Yes. They ask: "How Happy are You?" I Say: "I'm as happy as a stow away chimpanzee on a banana boat!"
|
|
|
|
Re: [nvda\] NVDA Devils advocate
Arlene
Exactly! When we did beta test jaws. We had to tell what version of windows we had. Back when Jaws was 5.0 there was windows xp, me, 98 and 95. So we had to say what we were using. Most or almost everybody was using xp from what I remember. We also had to say the version of beta we were using.
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Arlene observed, "Confirmed! If you have a certain bug. Some people can or can’t confirm your bug." Yep, because the number of variables that come into play to make certain bugs exhibit themselves are mind boggling (which is often why the software maker cannot replicate an issue even if they try to do so in what should be "the same environment" as it was encountered in by the user). We have folks with various versions of Windows, all sorts of different hardware, all sorts of assistive technology beyond NVDA potentially installed, all sorts of programs in general besides NVDA installed, and the list goes on. Each and every one of those things has the potential to set things up *juuuuuust right* for you, and only you (or a very small number of people who have the same combination as you), to encounter a given bug. I often think it's a bit of a miracle that most software functions at all given the number of variables at play that the developers have no control over and may have never even had a reason to conceive of. I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up. ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"
|
|
|
|
Re: signal or battery signal app
David Moore
With JAWS and NVDA, to read how much charge you have left in the battery
is:
NVDA or JAWS+SHIFT+B
From: Brian Vogel
Sent: Friday, June 3, 2016 6:26 PM
Subject: Re: [nvda] signal or battery signal app Issac, You're going to need to be a lot more explicit about the kind of signal you are trying to measure when you reference "signal tower." Also, what's a signal battery? You also might get a quicker
answer on the BlindTech group. I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up. ~ Trudy, in Jane
Wagner's "Search for Signs of Intelligent
Life in the Universe"
|
|
|
|
Re: signal or battery signal app
Issac, You're going to need to be a lot more explicit about the kind of signal you are trying to measure when you reference "signal tower." Also, what's a signal battery? You also might get a quicker answer on the BlindTech group. I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up. ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"
|
|
|
|
signal or battery signal app
Isaac <bigikemusic@...>
hi, anyone know of a signal tower or signal battery
app?
|
|
|
|
Re: NVDA Curiosity
Gene
I'm sure many people are using them. Unless
the developers start asking for more testers, it can be assumed that enough
testers are participating.
Gene
----- Original Message -----
I can see your point and I agree with you for the most part, but the beta versions of a product are only good if people are actually using them and reporting bugs. Chris
|
|
|
|
Re: NVDA Curiosity
Chris Shook <chris0309@...>
Jean,
I can see your point and I agree with you for the most part, but the beta versions of a product are only good if people are actually using them and reporting bugs. Chris
|
|
|
|
Re: NVDA Curiosity
n8mnx@att.net
I am not having any issues with nvda 2016.2 every version I have not yet encountered any issues.
toggle quoted messageShow quoted text
Brian Sackrider
On 6/3/2016 2:01 PM, Chris Shook wrote:
This goes along with my last post labeled NVDA devils advocate.
|
|
|
|
Re: NVDA Curiosity
Gene
I understand, but by the time a properly developed
and tested program reaches release, it will have been tested enough that it is
expected to function properly or without significant problems for most
users. That's why there are snapshots released more than once a week for
testing during development and that's why betas are released before
development.
Some people like to test programs while in
development. they may have annoyances or problems because of bugs while
the program is being developed. Interested people may spot problems or
express dissatisfaction with some aspects of the program during that time.
for people who want reliability and who don't want to test, the final release
version is the most likely to be the most bugg-free and reliable in the
development of the current version.
Gene----- Original Message
----- ----- Original Message -----
with the new NVDA because people that are having problems with the new NVDA usually report them. I wanted to see if problems were just with a few people or the majority. Chris
|
|
|
|
Re: NVDA Curiosity
Chris Shook <chris0309@...>
Just to clarify, I only asked how many people were not having problems with the new NVDA because people that are having problems with the new NVDA usually report them. I wanted to see if problems were just with a few people or the majority.
Chris
|
|
|
|
Re: NVDA Curiosity
Kwork
All good so far here as well. I haven't, and won't test everything as I
toggle quoted messageShow quoted text
don't have Office installed, but what I normally do is working just fine. Travis
----- Original Message -----
From: "Roger Stewart" <paganus2@gmail.com> To: <nvda@nvda.groups.io> Sent: Friday, June 03, 2016 11:29 AM Subject: Re: [nvda] NVDA Curiosity I'm having no problems with the newest nvda and I use Firefox and Thunderbird--no issues at all. Roger On 6/3/2016 1:01 PM, Chris Shook wrote: This goes along with my last post labeled NVDA devils advocate.
|
|
|
|
Re: NVDA success ( originally Curiosity)
Gene wrote: "And the original message didn't ask for messages of thanks or appreciation. It asked how many people are not having problems with NVDA. That is an entirely different request." Exactly. And this goes back to a case where I am in absolute agreement with you regarding thread titles. Putting "atta boys! (and girls, too)" in a thread that is a genuine attempt to see if others are encountering the same issue or issues in general with a release is a direct slap in the face to those having the troubles and trying their best to see if it might be idiosyncratic or more broadly based. I've been a programmer. It's nice to have praise and if you, for any you, want to start a thread for that purpose have at it. Don't hijack an issue identification thread because you think that the developers don't hear enough praise. That's not what they're paid (or volunteer) for and knowing what may be wrong is more helpful for creating a better and better product! P.S. The irony of my post and Gene's appearing in a thread that was specifically started as a praise thread is not lost on me. I also don't think this thread is a bad idea, either. -- I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up. ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"
|
|
|
|
Re: NVDA Curiosity
Kevin Cussick
good point agreed.
toggle quoted messageShow quoted text
On 03/06/2016 20:43, Gene wrote:
Such questions may generate a lot of meaningless responses. If 300 list
|
|
|
|
Re: NVDA success ( originally Curiosity)
Gene
I don't complain if some people express
appreciation off and on, as they do on list. But asking a general question
such as how many people are not having problems with NVDA doesn't provide useful
answers or information for developers. The developers have information
before the final release on the general performance of NVDA. that's an
important reason for releasing the RC or release candidates for testing
before the final version. It allows testing by a lot of people to see if
problems exist. If they do, the full version release may be delayed.
But the full version is released only after testing of the program indicates
that no problems of any significance exist that are known. But after a
full version is released, far more people use it. some problems that were
not known earlier are commonly discovered. That's what developers need to
know, what unexpected problems are found.
It's like asking people on a health list how many
people don't have headaches today. it provides no help nor useful
information to those who do.
And the original message didn't ask for messages of
thanks or appreciation. It asked how many people are not having problems
with NVDA. That is an entirely different request.
Gene
----- Original Message -----
From: Cearbhall O'Meadhra
Sent: Friday, June 03, 2016 3:09 PM
Subject: Re: [nvda] NVDA success ( originally
Curiosity) Gene,
I believe that there is a magnificent team of developers who need to know that their great work has delivered huge assistance to me and to all others who enjoy a trouble-free experience with NVDA 2016.2!
I think it is really important to keep reminding them that this is so.
As we in the computer world well know, there is always a new horizon to reach after the latest one has been reached. Therefore, I believe we should welcome those who are having trouble with the new release to explore the issue with open minds and offer all the means possible to collectively help to satisfy their needs. Some of their problems may have arisen because the new release has fixed the previous obstacles and now gives them the opportunity to go forward towards the functionality that they really want. This may bring up another stumbling block that has to be overcome. Such a discovery is not a negative for NVDA but a pointer to further growth.
I think the subject line should be separated to reflect these two conditions.
I use the free version of Spam Reader to get rid of spam. The Professional version doesn't have this disclaimer in outgoing emails. Try Spam Reader for free now!
From:
nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Gene
Such questions may generate a lot of meaningless responses. If 300 list members are not having problems. we will learn nothing useful by having them write to the list and saying they are not having probems. Problems need to be reported to be corrected. Nothing can be done when people write and say they are not having problems. It doesn't help solve the problems some people are having and such messages don't help NVDA function better.
Gee
This goes along with my last post
labeled NVDA devils advocate.
|
|
|
|
Re: NVDA Curiosity
Kevin Cussick
Hi, just at this moment nvda 2016.2 is working well for me with no problems.
toggle quoted messageShow quoted text
On 03/06/2016 19:01, Chris Shook wrote:
This goes along with my last post labeled NVDA devils advocate.
|
|
|
|
Reporting Issues to the NVDA Development Team
I think that what follows would be worth posting when release candidates are released and when an actual full release is released. A normal part of the software development process is to get bug reports. Although "zero defects" is the ideal, it is an ideal that I have never seen reached. While developers love to receive pats on the back, and deserve them, issue/bug reports are not considered a "slap in the face" but a helping hand, as users are certain to encounter things that were not encountered in testing - it goes with the territory. The direct link to the Github page for issue reporting for NVDA is: https://github.com/nvaccess/nvda/issues If you don't have a Github account you'll need to create on in order to officially log a suspected bug. When you click through to the page above, what you will be shown is a list of bugs/issues in open status. The filters edit box will be pre-populated with the following, which should be left there, "is:issue is:open" and this is what gives you only open issues. That being said, it's not worth opening a new issue if one already exists identifying your problem. So, it's well worth putting in a search term (or two) after those prepopulated ones to see if a problem that matches yours may already be logged. Let's say you have an issue with pronunciation, then enter "pronunciation" (no quotes, of course) after the prepopulated terms and hit Enter. Now the list shown will be limited to ones that have the word "pronunciation" in their title or actual report text. You could use search terms like "iTunes", "Firefox", etc., and you can use more than one, so something like "iTunes 12" would be just fine. If there's a problem that already matches yours, activate that link to read up on it and/or possibly leave an additional comment to let the developers know that you've also encountered it along with information regarding the operating system, NVDA version, and other details needed to help them track it down and squash the bug. If your problem doesn't appear to be in the list, find and activate the "New Issue" button, which will present you with a webpage that places you in an edit box for the title you wish to use (please be specific - titles like "Problem encountered" don't help anyone) and then an edit box where you enter a detailed description. Ideally, if you can make the problem recur reliably, you give the steps you take to make it occur each time it occurs. Doing the above is one way to contribute to the ongoing NVDA development efforts in a very positive way. -- I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up. ~ Trudy, in Jane Wagner's "Search for Signs of Intelligent Life in the Universe"
|
|
|
|
Re: Weird issue
Danni
No because sometimes I can hear colors or options and sometimes I can't! which tells me something is going on I just don't know what!
toggle quoted messageShow quoted text
----- Original Message -----
From: "Andre Fisher" <andrefisher729@gmail.com> To: <nvda@nvda.groups.io> Sent: Friday, June 03, 2016 8:46 AM Subject: Re: [nvda] Weird issue Maybe the site's layout was changed, don't you think?
|
|
|
|
Re: NVDA success ( originally Curiosity)
Cearbhall O'Meadhra
Gene,
I believe that there is a magnificent team of developers who need to know that their great work has delivered huge assistance to me and to all others who enjoy a trouble-free experience with NVDA 2016.2!
I think it is really important to keep reminding them that this is so.
As we in the computer world well know, there is always a new horizon to reach after the latest one has been reached. Therefore, I believe we should welcome those who are having trouble with the new release to explore the issue with open minds and offer all the means possible to collectively help to satisfy their needs. Some of their problems may have arisen because the new release has fixed the previous obstacles and now gives them the opportunity to go forward towards the functionality that they really want. This may bring up another stumbling block that has to be overcome. Such a discovery is not a negative for NVDA but a pointer to further growth.
I think the subject line should be separated to reflect these two conditions.
I use the free version of Spam Reader to get rid of spam. The Professional version doesn't have this disclaimer in outgoing emails. Try Spam Reader for free now!
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: Friday, June 3, 2016 8:43 PM To: nvda@nvda.groups.io Subject: Re: [nvda] NVDA Curiosity
Such questions may generate a lot of meaningless responses. If 300 list members are not having problems. we will learn nothing useful by having them write to the list and saying they are not having probems. Problems need to be reported to be corrected. Nothing can be done when people write and say they are not having problems. It doesn't help solve the problems some people are having and such messages don't help NVDA function better.
Gee
This goes along with my last post labeled NVDA devils advocate.
|
|
|
