Dear all,

after months of activity in this community I have discovered a lot of interesting discussions and opinions in Github when looking through several NVDA issues which are open since more than 5 years. And as most of you might already know, there are over 2250 issues open at this time. Unfortunately there are a lot of discussions which are not updated. There are a lot of issues which actually are solved or propably solved but are still open. Many people in this list created different issues related to NVDA on Github. But at the same time, many people did not care about those issues and they did not test if they still occur with last NVDA versions.

I would like to encourage you all who created issues on Github: please answer our questions on Github when we comment on your issues. If you are not using the old software that you created issues for, please take 10 minutes of your life and installt the last version and try to reproduce the issue again. Please comment on your issues and tell us if it is reproducible or not. I can talk at least for myself, I spend sometime hours to restart discussions on old issues or to try to get answers from involved people. But most of them do not react. This is indeed frustrating because in one or two years someone else will ask the same questions and in the end we will have far too much issues which are just noise or low quality.

This message is also for all developers who are or were involved in old issues. Please take some minutes and continue discussions or answer our questions when we try to decide how to deal with a certain issue. This helps us to decide if issues can be closed or not.

The issue page for NVDA on github is very overloaded and this makes it also very difficult to atribute certain pull requests to certain issues. Let us work together and transform the quantity of issues in quality. This will make it easier for developers to see where they can work for. For users, a better overview will lead to less duplicate issues and to less frustration.

Thank you very much for your attention.

Best regards

Adriani

Does anyone know if the person reporting this issue has tried the visual
studio add-on for nvda?

Development on this add-on has stagnated, but I believe 2010 is supported
and it may do some good.

I don't program in visual basic, but I do use visual studio on a daily
basis, and most of it works very well. I am using visual studio 2017 and
that may make a huge difference. It's not super feasible to support 8 year
old versions of software. I think it's safe to say, jaws is heavily
scripted for visual studio 2010. I think it's also fair to say that
Microsoft in-house concern over accessibility has taken many leaves forward

in the past 8 years. it certainly is not where it completely needs to be
at this point, but I think you might get a lot more mileage out of
upgrading if at all possible.

Best,

Erik


On November 26, 2018 8:41:24 PM "Quentin Christensen"
<quentin@nvaccess.org> wrote:

Hi,

As Adriani noted, there are a couple of issues on GitHub which could be
similar. A couple of questions to follow up:

You said several different versions of NVDA - so this is not a new issue,
it has been present for some time? Did it used to work at one point, or
has it always been a problem?

Does it cause an error or a crash, in either NVDA or Visual Studio, or make
NVDA unresponsive - aside from not being able to read text in Visual
Studio, if you say, alt+tab to another window does NVDA work?

If you could set NVDA's log level to "debug", then repeat the program with
NVDA, and then email me a copy of your NVDA log to info@nvaccess.org, that
would be very helpful please.

There is some info on our log files here:
https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps

Kind regards

Quentin.

On Sat, Nov 24, 2018 at 8:14 AM abdul muhamin <abdulmuhamin600@gmail.com>
wrote:

I’m forwarding this e mail for someone’s
behalf






*From: *Raha Tehrani <raha.tehrani1362@gmail.com>
*Sent: *Saturday, November 24, 2018 1:30 AM
*To: *bhp <bhp@groups.io>
*Subject: *[bhp] NVDA



Dear all.

as you all know, NVDA 2018.4 is on the way. at the moment, the

developers' version is available to check for probable problems.

there's a problem which I have seen with different versions of NVDA.

it won't say anything in Visual Basic in Microsoft visual studio. I

have tried it on Microsoft visual studio 2010. it's fine with the

design area. but it keeps being completely silent while the text

editor area is on the foreground. I have no account on Github. but if

you have one, please let them know about this very significant

problem, so that it can be fixed in the next release. it's kind of

important. because you can't simply edit what you write within the

text-editing environment. as a result, programming gets difficult on

visual basic in microsoft visual studio 2010, using NVDA. please do

tell the NVAccess team about this major problem. note: this is not the

case with JAWS. it's fine with VB in MS Visual Studio 2010. you can

easily move with design and text-editing area with jaws. therefore,

you can easily edit what you've written in the text editor

environment.

take care.

--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

On Mon, Nov 26, 2018 at 11:34 PM, Vlad Dragomir wrote:

It shouldn’t be hard to do.

Well, and not for the purpose of being nasty or contrary, nothing
could be further from the truth.

This is a particular instance where no matter what the accessibility
workaround it is taking a medium meant to be accessed by sight, really
only accessed by sight, that is a transcription of sound.  It is
particularly and peculiarly unsuited to any methods currently known
and the only thing I can think of would be if one could get a
synthesizer to read the IPA graphemes as phonemes, one-by-one, and
even that doesn't come close to connected speech.

I have said, on many occasions, that sometimes there is no substitute
for sight and that all accessibility is a workaround which imposes
specific limitations not posed by media being "consumed" in the
sensory modality for which it was explicitly designed.

--

Brian *-*Windows 10 Home, 64-Bit, Version 1809, Build 17763

*/A great deal of intelligence can be invested in ignorance when the
need for illusion is deep./*

          ~ Saul Bellow, /To Jerusalem and Back/

so Brian, you are one of the few people who know what I got myself into then.  I think I can write the morphology assignment with no phonetics. Moreover, as I will do my thesis on pragmatics, I will not use more phonetics for the rest of my master. But I want to eventually learn the alphabet, as I want to do a doctorate in linguistics.

On 11/27/2018 1:44 AM, Brian Vogel wrote:

On Mon, Nov 26, 2018 at 02:16 PM, Brian's Mail list account wrote:

So the concept is then, trying to put sounds into a writable form for a person who cannot see it in the first place. This sounds a bit like some kind comedy sketch from an old goon show.

Precisely.

I also don't know how to explain that we who see and are examining material in the IPA are not trying to read it, but are really using it to "sound it out."

As you're also a Brian, you know what our shared name sounds like.  It would be written in IPA so that linguists, or non-native speakers of a given language, can sound out how we pronounce it.  No one ever reads it character by character using the actual IPA character name, but using the sound (AKA phoneme) that the character represents.

The list that John Isige presented is not comprehensive, either (and, John, that's not a swipe at you, it's just an observation).  A number of the common vowel digraphs of English are missing.

All of this takes me back to when I was studying speech and language pathology for my master's and put together a child-language checksheet for order of acquisition of various English phonemes, morphological markers, as well as interactional skills/communicative intents (among other things).

--

Brian - Windows 10 Home, 64-Bit, Version 1809, Build 17763  

A great deal of intelligence can be invested in ignorance when the need for illusion is deep.

          ~ Saul Bellow, To Jerusalem and Back

 

 

Hi, wondering noticed that OCR not working if all the addons is enabled.
I tested to disable all the addons and it works. to read the OCR
functions.
I am currently using NVDA version 2018.4beta2
Does anyone noticed this? Thanks.
I list down all the addons that I installed to my NVDA for reference:

Add-on Updater;
Emoticons;
Focus Highlight;
TeamTalk Classic Fixes;
Remote Support;
TextNav;
Windows 10 App Essentials;

no, it works in my situation correctly.
no difference if add-ons are enabled or disabled.
try to uninstall nvda, removethe map of nvda manually if necessary
then renew the installation of nvda.
and see if the problem is gone.
cheers
paul otter


Op 27-11-2018 om 12:07 schreef Robert Mendoza:

Hi, wondering noticed that OCR not working if all the addons is enabled.
I tested to disable all the addons and it works. to read the OCR functions.
I am currently using NVDA version 2018.4beta2
Does anyone noticed this? Thanks.
I list down all the addons that I installed to my NVDA for reference:

Add-on Updater;
Emoticons;
Focus Highlight;
TeamTalk Classic Fixes;
Remote Support;
TextNav;
Windows 10 App Essentials;

With access technology institute, you are definitely paying for a brand.
I've used them. It is an outstanding brand! it's not cheap, and I realize not everyone can afford it, but sometimes it's okay to charge what something is worth. Regardless of where the materials come from, a lot of time and effort go in to their preparation. the reason why you would pay high prices for these books is that if you've used the access technology institute for many years and you're used to the training style, then you would want to keep dealing with them. Otherwise, you may want to save money and go with the equally valuable materials that come directly from NV access for a lower price, the manual, online forums, and this email list as references.

You would hope that something comes back from ATI to envy access from the purchase of these textbooks, but I wouldn't count on it. At least, if you buy textbooks directly from envy access, you know you're supporting the product.

personally, I'm a little gratified that they cared enough to make the materials. Most business class organizations are still focused on Jaws despite the tremendous benefits of nvda.

I hope ATI sells a ton of their textbooks to businesses, rehabilitation agencies, and other groups who love paying a lot of money for ...stuff.


On November 26, 2018 4:53:10 PM "Sue J. Ward" <groovy41@juno.com> wrote:

Hello. I would like to buy the two books about NVDA but they are kind
of pricey maybe email them to me if you can on the blind.training or it
is called access technology institute website. One is about the NVDA
screen reader which goes for 95 dollars that mainly talks about the
entire screen reader guess from what I have read it walks you through
everything the only thing I don't know when it was written. Does any one
have a copy that could email it to me for free? The other one is about
windows 10 using nvda it sounds like it is a good book to get it talks
about the entire system but what I don't get is when you first get a new
computer that has windows 10 it does not have word installed and in the
book it mentions and walks you through windows 10 and one of the lessons
is managing and saving documents mentions word plus there are several
lessons about microsoft word. It is good but I just want a book mainly
about windows 10 minus the stuff about word. The book does cost around
150 dollars it sounds like a good resource was wondering has anyone
bought the books from the website and how good are they? I would also
like a copy of the book as well if anyone has that could they email that
to me? The books are an immersion in to NVDA

The other one is an immersion in to windows 10 with NVDA. Thank you.
____________________________________________________________
How CBD Oil “Healed Her Painâ€&#65533; When Nothing Else Helped
CDX Labs
http://thirdpartyoffers.juno.com/TGL3131/5bfc6b0365c286b035e8cst04vuc