Bard Express with NVDA2017.1 RC?


Gerardo Corripio <gera1027@...>
 

For anyone using Bard Express with NVDA 2017.1 rc, are the lists still truncated? in case the NVDA devs can fix this annoyance before the final NVDA2017.1 release that is.


--
Gera
Enviado desde Thunderbird


 

This is a bard express design issue. It is not an NVDA issue. send feedback to the bard express team.


Andre Fisher
 

Furthermore, there will be no fixes to the feature set of NVDA 2017.1.
This is a release candidate, so it is identical to the 2017.1 final
release, unless critical issues are found.

On 2/15/17, Robert Kingett <kingettr@...> wrote:
This is a bard express design issue. It is not an NVDA issue. send
feedback to the bard express team.




Brian's Mail list account
 

That depends what you call an issue of course.
Its often hard when you have the program makers saying they have no issuees and the screenreader maker saying oh yes you have of course.
The thing is that to cludge nvda to make something work when a piece of software is still being developed can have its drawbacks. Look at how often Skype manages to fix one thing, then screw up something else. Some software teams are just not testing with the screen readers. Just note what has happened to Revo and some of the malware programs to see the issues.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Andre Fisher" <andrefisher729@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, February 15, 2017 4:32 PM
Subject: Re: [nvda] Bard Express with NVDA2017.1 RC?


Furthermore, there will be no fixes to the feature set of NVDA 2017.1.
This is a release candidate, so it is identical to the 2017.1 final
release, unless critical issues are found.

On 2/15/17, Robert Kingett <kingettr@...> wrote:
This is a bard express design issue. It is not an NVDA issue. send
feedback to the bard express team.




Quentin Christensen
 

As Andre mentioned, there won't be any change to NVDA's features prior to 2017.1 now.  The reason for this is that when something is fixed, or changed, or added, it goes into testing where it is available to users who choose to test features first.  Once it has been available in that environment for a couple of weeks and no major problems have been found, then it gets considered for inclusion into the next stable version of NVDA.  We would hate to roll out a new version with some brand new, untested features, only to find that they cause major problems for a (possibly unrelated) group of users.

What I would recommend, is to create an issue on our issue tracker: https://github.com/nvaccess/nvda/issues  That way you will be notified of any investigations into the problem as well as if and when a solution is developed.

Kind regards

Quentin.

On Thu, Feb 16, 2017 at 12:52 AM, Gerardo Corripio <gera1027@...> wrote:
For anyone using Bard Express with NVDA 2017.1 rc, are the lists still truncated? in case the NVDA devs can fix this annoyance before the final NVDA2017.1 release that is.


--
Gera
Enviado desde Thunderbird







--
Quentin Christensen
Training Material Developer
Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

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