Date   

Re: Can one re register all dlls in the windows folders safely?

Gene New Zealand <hurrikennyandopo@...>
 

Hi Brian


From what i have been looking up it is a messy process. there are
certain ones they refer to of which i think the tool fixes in NVDA.


Apart from that i see the reference to reinstalling windows. I guess it
depends how bad your copy  of windows is before you go that far.


What again is drop box not doing?


I have the application drop box on the computer and when i go into it i
can see the different folders and the files with in the folder.

But am sure when i go to delete folders or files it used to give a
message. I am using the latest version of Windows 10 stable 1709 i think
it is along with nvda 2018.2.1


I can get to the message with object navigation though.

But there are new comers to nvda that would not even know how to use
object navigation .



But i can not remember before when you found a file it said the message
do you want to delete this file and send it to the rubbish bin. I notice
it only gives you the option to either click on yes or no but the
message is not read out. I thought it used to be?

If this is the case either some thing has become unchecked in NVDA to do
this  or a bug has creeped in.


Gene nz

On 7/5/2018 7:39 AM, Brian's Mail list account via Groups.Io wrote:
I don't know how to do it, but I did hear a guy on a video doing it
but he seemed to have to back them all up first and unfortunately as
you can see here is not best for a blindy.

If it can be done safely, is there a tool for this I can use? Remember
I do not want to change any, I've already run sfc /scannow and had to
reinstall the email software afterwards. I'm assuming this does not
check if the dlls are registered.
The whole idea is of course to attempt to get nvda to see the dropbox
dialogues. I'm running out of options here and yes I have run the 
file register utility in nvda with no sign of any improvements.
If I can do this safely, and that does not cure the issue, I'm open to
suggestions except installing windows 10 on this machine. I have
reasons for not doing it which are too complex to explain.
Thanks I await the experts to inform me what to do. I could not find
much on Microsoft's site, maybe I'm looking for the wrong thing!

Brian

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



test

Gary Metzler
 

Just testing.

 

Regards, Gary KN4Ox

Send to: gmtravel@...

 


Re: New release system and new snapshot names from Mick

Kevin Cussick
 

well, after reading about this I think I agree with the devs. I am also pleased to see Nvda improving the way it is being updated. I would hope that most people who run master or the new beta are aware that things may not work as expected.

On 04/07/2018 07:36, Brian's Mail list account via Groups.I wrote:
From: "Mick Curran" <mick@...>
To: "NVDA screen reader development" <nvda-devel@...>;
<nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process

Hi contributors,


We have made some small changes to the NVDA release process. Please read
the updated Release Process article carefully to understand the changes
and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be merged
straight to master. Periodic betas will be offered startin from 5 weeks
before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch rather than
master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Brian comments. I think this is actually going to affect people on this list
like myself who use the bleeding edge code as portable versions and master
as a daily working version.
I worry a little hear about a large number of untested by users items
arriving in the beta all at once  which might be a little scary if a lot of
people find issues. At the moment they hit next regularly and one can see
the wood for the trees so to speak.
If you have any comments, send them to Mick not me though, as I do not see
any kind of consultation with users on this one.
Brian
bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.


Can one re register all dlls in the windows folders safely?

Brian's Mail list account <bglists@...>
 

I don't know how to do it, but I did hear a guy on a video doing it but he seemed to have to back them all up first and unfortunately as you can see here is not best for a blindy.

If it can be done safely, is there a tool for this I can use? Remember I do not want to change any, I've already run sfc /scannow and had to reinstall the email software afterwards. I'm assuming this does not check if the dlls are registered.
The whole idea is of course to attempt to get nvda to see the dropbox dialogues. I'm running out of options here and yes I have run the file register utility in nvda with no sign of any improvements.
If I can do this safely, and that does not cure the issue, I'm open to suggestions except installing windows 10 on this machine. I have reasons for not doing it which are too complex to explain.
Thanks I await the experts to inform me what to do. I could not find much on Microsoft's site, maybe I'm looking for the wrong thing!

Brian

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


Re: New release system and new snapshot names from Mick

Brian's Mail list account <bglists@...>
 

Hmm, yes but I think at the changeover all those who use master and assume its almost beta quality might need a nudge from a popup or something to tell them the changes. may not read here regularly of course.
Brian

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

----- Original Message -----
From: "Jason White via Groups.Io" <jason=jasonjgw.net@groups.io>
To: <nvda@nvda.groups.io>
Sent: Wednesday, July 04, 2018 5:40 PM
Subject: Re: [nvda] New release system and new snapshot names from Mick


It's encouraging that NV Access is making progress toward greater automated regression testing, improved code review procedures, and a better release process.

On 7/4/18, 07:39, "Brian's Mail list account via Groups.Io" <nvda@nvda.groups.io on behalf of bglists=blueyonder.co.uk@groups.io> wrote:


A reply from Mick. I have also added my comments to Josephs translations
sub line earlier as it really does not flag up the extent this change may
affect normal users of snapshots here .

===
He writes:
Hi Brian,


I appreciate your constructive feedback. We will certainly think about
your proposal and see what we can manage.

Although we have published the new process, we have not yet removed any
branches or switched anyone over, so we can still make some changes
before committing to this fully.


The reasons for sticking with the name master for the default
development branch are:

1. We don't want to break existing pull requests which are currently
open against master. There are more than 40 or so.

2. We don't want new contributors submitting pull requests against an
old (defunct) version of master (if we do move).

3. master is the generally accepted name for the default branch of git
repositories for most projects on github.


There may be another way to solve this specifically for snapshots. I'll
have to research this further.


We will wait for more feedback and think on this more.


Mick





But,




On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:
> While I can see the reasoning for this change. I do think that a number of
> us are going to have to do the following. When the Next becomes master, we
> are going to have a period when the new beta branch does not exist, Now
> taking my own case as a for instance. I currently use master as my working
> version though I of course do have a portable of the latest stable
> version, That will mean if I do nothing result in effectively my master
> becoming next, which means my normal copy is now bleeding edge code. I may
> have to wait till the new beta is created for the ability to change this
> around, and make next master and master beta. Would it not be more
> sensible to just remove master, and use next as you propose master is to
> be, then create a new beta when applicable?
> That way folk used to using master as pretty stable will not be affected.
> They will stay on master, then when a new beta comes out they will be
> migrated to this for their working versions.
> if you want users to participate, as I think is a good thing, in my view
> the proposal I outline above will carry more people with you. also please
> remember to formerly tell people on the user list about what you are doing
> so you do not suddenly find a lot of folk with problems.
> I do realise that there are now a lot more checks done automatically, but
> in the end its the user that will be running the code more than anyone
> else, and feedback from that cohort of people is worth its weight in gold.
> we all know that many programmers are the worst testers as they are
> predictable. its the newbie and the less confident user who finds the
> bugs.
> So what do you think?
>
> Brian
>
> bgaff@...
> Brian Gaff's other account.
>
> ----- Original Message ----- From: "Mick Curran" <mick@...>
> To: "NVDA screen reader development" <nvda-devel@...>;
> <nvda-translations@groups.io>
> Sent: Wednesday, July 04, 2018 2:43 AM
> Subject: [Nvda-devel] Changes to release process
>
>
>> Hi contributors,
>>
>>
>> We have made some small changes to the NVDA release process. Please read
>> the updated Release Process article carefully to understand the changes
>> and how they will affect you.
>>
>> https://github.com/nvaccess/nvda/wiki/ReleaseProcess
>>
>>
>> In short, Next/incubation is going away, and prs are going to be merged
>> straight to master. Periodic betas will be offered startin from 5 weeks
>> before a release.
>>
>> Please read the entire article to understand the changes fully.
>>
>>
>> Translators should not be directly affected by this change. Though
>> technically, translations are now based on a new "beta" branch rather
>> than master.
>>
>>
>> Mick
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> --
>> Mick Curran
>> Executive Director, NV Access Limited
>> PH: +61 7 3149 3306 ext. 101
>> www: http://www.nvaccess.org/
>> Twitter: @NVAccess
>> Facebook: http://www.facebook.com/NVAccess
>>
>>
>> ------------------------------------------------------------------------------
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvda-devel@...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>
>
> ------------------------------------------------------------------------------
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> Nvda-devel@...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel

--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Brian's Mail list account via Groups.Io"
<bglists=blueyonder.co.uk@groups.io>
To: <nvda@groups.io>
Sent: Wednesday, July 04, 2018 7:36 AM
Subject: [nvda] New release system and new snapshot names from Mick


> From: "Mick Curran" <mick@...>
> To: "NVDA screen reader development" <nvda-devel@...>;
> <nvda-translations@groups.io>
> Sent: Wednesday, July 04, 2018 2:43 AM
> Subject: [Nvda-devel] Changes to release process
>
>
>> Hi contributors,
>>
>>
>> We have made some small changes to the NVDA release process. Please read
>> the updated Release Process article carefully to understand the changes
>> and how they will affect you.
>>
>> https://github.com/nvaccess/nvda/wiki/ReleaseProcess
>>
>>
>> In short, Next/incubation is going away, and prs are going to be merged
>> straight to master. Periodic betas will be offered startin from 5 weeks
>> before a release.
>>
>> Please read the entire article to understand the changes fully.
>>
>>
>> Translators should not be directly affected by this change. Though
>> technically, translations are now based on a new "beta" branch rather
>> than
>> master.
>>
>>
>> Mick
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> --
>> Mick Curran
>> Executive Director, NV Access Limited
>> PH: +61 7 3149 3306 ext. 101
>> www: http://www.nvaccess.org/
>> Twitter: @NVAccess
>> Facebook: http://www.facebook.com/NVAccess
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvda-devel@...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
> Brian comments. I think this is actually going to affect people on this
> list
> like myself who use the bleeding edge code as portable versions and master
> as a daily working version.
> I worry a little hear about a large number of untested by users items
> arriving in the beta all at once which might be a little scary if a lot
> of
> people find issues. At the moment they hit next regularly and one can see
> the wood for the trees so to speak.
>
> If you have any comments, send them to Mick not me though, as I do not see
> any kind of consultation with users on this one.
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
>
>
>


Re: New release system and new snapshot names from Mick

Jason White
 

It's encouraging that NV Access is making progress toward greater automated regression testing, improved code review procedures, and a better release process.

On 7/4/18, 07:39, "Brian's Mail list account via Groups.Io" <nvda@nvda.groups.io on behalf of bglists=blueyonder.co.uk@groups.io> wrote:


A reply from Mick. I have also added my comments to Josephs translations
sub line earlier as it really does not flag up the extent this change may
affect normal users of snapshots here .

===
He writes:
Hi Brian,


I appreciate your constructive feedback. We will certainly think about
your proposal and see what we can manage.

Although we have published the new process, we have not yet removed any
branches or switched anyone over, so we can still make some changes
before committing to this fully.


The reasons for sticking with the name master for the default
development branch are:

1. We don't want to break existing pull requests which are currently
open against master. There are more than 40 or so.

2. We don't want new contributors submitting pull requests against an
old (defunct) version of master (if we do move).

3. master is the generally accepted name for the default branch of git
repositories for most projects on github.


There may be another way to solve this specifically for snapshots. I'll
have to research this further.


We will wait for more feedback and think on this more.


Mick





But,




On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:
> While I can see the reasoning for this change. I do think that a number of
> us are going to have to do the following. When the Next becomes master, we
> are going to have a period when the new beta branch does not exist, Now
> taking my own case as a for instance. I currently use master as my working
> version though I of course do have a portable of the latest stable
> version, That will mean if I do nothing result in effectively my master
> becoming next, which means my normal copy is now bleeding edge code. I may
> have to wait till the new beta is created for the ability to change this
> around, and make next master and master beta. Would it not be more
> sensible to just remove master, and use next as you propose master is to
> be, then create a new beta when applicable?
> That way folk used to using master as pretty stable will not be affected.
> They will stay on master, then when a new beta comes out they will be
> migrated to this for their working versions.
> if you want users to participate, as I think is a good thing, in my view
> the proposal I outline above will carry more people with you. also please
> remember to formerly tell people on the user list about what you are doing
> so you do not suddenly find a lot of folk with problems.
> I do realise that there are now a lot more checks done automatically, but
> in the end its the user that will be running the code more than anyone
> else, and feedback from that cohort of people is worth its weight in gold.
> we all know that many programmers are the worst testers as they are
> predictable. its the newbie and the less confident user who finds the
> bugs.
> So what do you think?
>
> Brian
>
> bgaff@...
> Brian Gaff's other account.
>
> ----- Original Message ----- From: "Mick Curran" <mick@...>
> To: "NVDA screen reader development" <nvda-devel@...>;
> <nvda-translations@groups.io>
> Sent: Wednesday, July 04, 2018 2:43 AM
> Subject: [Nvda-devel] Changes to release process
>
>
>> Hi contributors,
>>
>>
>> We have made some small changes to the NVDA release process. Please read
>> the updated Release Process article carefully to understand the changes
>> and how they will affect you.
>>
>> https://github.com/nvaccess/nvda/wiki/ReleaseProcess
>>
>>
>> In short, Next/incubation is going away, and prs are going to be merged
>> straight to master. Periodic betas will be offered startin from 5 weeks
>> before a release.
>>
>> Please read the entire article to understand the changes fully.
>>
>>
>> Translators should not be directly affected by this change. Though
>> technically, translations are now based on a new "beta" branch rather
>> than master.
>>
>>
>> Mick
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> --
>> Mick Curran
>> Executive Director, NV Access Limited
>> PH: +61 7 3149 3306 ext. 101
>> www: http://www.nvaccess.org/
>> Twitter: @NVAccess
>> Facebook: http://www.facebook.com/NVAccess
>>
>>
>> ------------------------------------------------------------------------------
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvda-devel@...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
>
>
> ------------------------------------------------------------------------------
>
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nvda-devel mailing list
> Nvda-devel@...
> https://lists.sourceforge.net/lists/listinfo/nvda-devel

--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Brian's Mail list account via Groups.Io"
<bglists=blueyonder.co.uk@groups.io>
To: <nvda@groups.io>
Sent: Wednesday, July 04, 2018 7:36 AM
Subject: [nvda] New release system and new snapshot names from Mick


> From: "Mick Curran" <mick@...>
> To: "NVDA screen reader development" <nvda-devel@...>;
> <nvda-translations@groups.io>
> Sent: Wednesday, July 04, 2018 2:43 AM
> Subject: [Nvda-devel] Changes to release process
>
>
>> Hi contributors,
>>
>>
>> We have made some small changes to the NVDA release process. Please read
>> the updated Release Process article carefully to understand the changes
>> and how they will affect you.
>>
>> https://github.com/nvaccess/nvda/wiki/ReleaseProcess
>>
>>
>> In short, Next/incubation is going away, and prs are going to be merged
>> straight to master. Periodic betas will be offered startin from 5 weeks
>> before a release.
>>
>> Please read the entire article to understand the changes fully.
>>
>>
>> Translators should not be directly affected by this change. Though
>> technically, translations are now based on a new "beta" branch rather
>> than
>> master.
>>
>>
>> Mick
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> --
>> Mick Curran
>> Executive Director, NV Access Limited
>> PH: +61 7 3149 3306 ext. 101
>> www: http://www.nvaccess.org/
>> Twitter: @NVAccess
>> Facebook: http://www.facebook.com/NVAccess
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Nvda-devel mailing list
>> Nvda-devel@...
>> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>>
> Brian comments. I think this is actually going to affect people on this
> list
> like myself who use the bleeding edge code as portable versions and master
> as a daily working version.
> I worry a little hear about a large number of untested by users items
> arriving in the beta all at once which might be a little scary if a lot
> of
> people find issues. At the moment they hit next regularly and one can see
> the wood for the trees so to speak.
>
> If you have any comments, send them to Mick not me though, as I do not see
> any kind of consultation with users on this one.
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
>
>
>


test

Gary Metzler
 

Just testing.


Re: New release system and new snapshot names from Mick

Brian's Mail list account <bglists@...>
 

A reply from Mick. I have also added my comments to Josephs translations sub line earlier as it really does not flag up the extent this change may affect normal users of snapshots here .

===
He writes:
Hi Brian,


I appreciate your constructive feedback. We will certainly think about
your proposal and see what we can manage.

Although we have published the new process, we have not yet removed any
branches or switched anyone over, so we can still make some changes
before committing to this fully.


The reasons for sticking with the name master for the default
development branch are:

1. We don't want to break existing pull requests which are currently
open against master. There are more than 40 or so.

2. We don't want new contributors submitting pull requests against an
old (defunct) version of master (if we do move).

3. master is the generally accepted name for the default branch of git
repositories for most projects on github.


There may be another way to solve this specifically for snapshots. I'll
have to research this further.


We will wait for more feedback and think on this more.


Mick





But,




On 4/07/2018 4:59 PM, Brians old account via Nvda-devel wrote:
While I can see the reasoning for this change. I do think that a number of us are going to have to do the following. When the Next becomes master, we are going to have a period when the new beta branch does not exist, Now taking my own case as a for instance. I currently use master as my working version though I of course do have a portable of the latest stable version, That will mean if I do nothing result in effectively my master becoming next, which means my normal copy is now bleeding edge code. I may have to wait till the new beta is created for the ability to change this around, and make next master and master beta. Would it not be more sensible to just remove master, and use next as you propose master is to be, then create a new beta when applicable?
That way folk used to using master as pretty stable will not be affected. They will stay on master, then when a new beta comes out they will be migrated to this for their working versions.
if you want users to participate, as I think is a good thing, in my view the proposal I outline above will carry more people with you. also please remember to formerly tell people on the user list about what you are doing so you do not suddenly find a lot of folk with problems.
I do realise that there are now a lot more checks done automatically, but in the end its the user that will be running the code more than anyone else, and feedback from that cohort of people is worth its weight in gold. we all know that many programmers are the worst testers as they are predictable. its the newbie and the less confident user who finds the bugs.
So what do you think?

Brian

bgaff@...
Brian Gaff's other account.

----- Original Message ----- From: "Mick Curran" <mick@...>
To: "NVDA screen reader development" <nvda-devel@...>; <nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please read the updated Release Process article carefully to understand the changes and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be merged straight to master. Periodic betas will be offered startin from 5 weeks before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though technically, translations are now based on a new "beta" branch rather than master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: <nvda@groups.io>
Sent: Wednesday, July 04, 2018 7:36 AM
Subject: [nvda] New release system and new snapshot names from Mick


From: "Mick Curran" <mick@...>
To: "NVDA screen reader development" <nvda-devel@...>;
<nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please read
the updated Release Process article carefully to understand the changes
and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be merged
straight to master. Periodic betas will be offered startin from 5 weeks
before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch rather than
master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Brian comments. I think this is actually going to affect people on this list
like myself who use the bleeding edge code as portable versions and master
as a daily working version.
I worry a little hear about a large number of untested by users items
arriving in the beta all at once which might be a little scary if a lot of
people find issues. At the moment they hit next regularly and one can see
the wood for the trees so to speak.

If you have any comments, send them to Mick not me though, as I do not see
any kind of consultation with users on this one.
Brian

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


Re: Cannot press c or shift+C to jump to combobox

Brian's Mail list account <bglists@...>
 

And it goes into focus mode and then can be selected from in waterfox I think.
I had this same authoring error on a charity website the other week as well, its been fixed now along with exposing static text as an edit area with hilarious results, not intended by the writer!
Brian

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

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda@nvda.groups.io>
Sent: Wednesday, July 04, 2018 4:33 AM
Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox


Hi,

Ah, the control in question is exposed as a list box, for which NVDA does
not recognize as a combo box.

Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dang Manh Cuong
Sent: Tuesday, July 3, 2018 8:29 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox



Hi

You can try this: https://saomaicenter.org/en/downloads

----------------
Dang Manh Cuong
The Assistive technology specialist
Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
Tel: +8428 7302-4488
E-mail: vanphong@... <mailto:vanphong@...> ;
congnghe@... <mailto:congnghe@...>
Facebook: https://www.facebook.com/saomaicenterfortheblind
Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org Mobile
/ Zalo: +84 902-572-300
E-mail: @cuongdang <mailto:@cuongdang> ;
cuong@... <mailto:cuong@...>
Skype name: dangmanhcuong
facebook: http://facebook.com/dangmanhcuong
Twitter: @ManhCuongTech

----- Original Message -----

From: Joseph Lee <mailto:@joslee>

To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>

Sent: Wednesday, July 04, 2018 10:07 AM

Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox



Hi,

Do you have an example website where we can try reproducing this? Thanks.

Cheers,

Joseph



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io
<mailto:nvda@nvda.groups.io> > On Behalf Of Dang Manh Cuong
Sent: Tuesday, July 3, 2018 8:02 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] Cannot press c or shift+C to jump to combobox



To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in
web page created using drupal. This also occurs when I use driver pack a
program for searching driver. NVDA just sayy no comboboxes, but I can jump
to it using tab or arrows. Seeing this problem with Firefox, Internet
explorer, crhome and Microsoft edge.

I think this is not enough to create issue on gidhub so I share here, and
I'll research more before submitting an issue. Hope you can pick time
research this with me.
Cuong

----------------
Dang Manh Cuong
The Assistive technology specialist
Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
Tel: +8428 7302-4488
E-mail: vanphong@... <mailto:vanphong@...> ;
congnghe@... <mailto:congnghe@...>
Facebook: https://www.facebook.com/saomaicenterfortheblind
Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org Mobile
/ Zalo: +84 902-572-300
E-mail: @cuongdang <mailto:@cuongdang> ;
cuong@... <mailto:cuong@...>
Skype name: dangmanhcuong
facebook: http://facebook.com/dangmanhcuong
Twitter: @ManhCuongTech






Re: Cannot press c or shift+C to jump to combobox

Brian's Mail list account <bglists@...>
 

Are there any on this page? I can see selections that look like lists in focus mode on the page, but they are not in fact combo boxes.
Brian

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

----- Original Message -----
From: "Dang Manh Cuong" <@cuongdang>
To: <nvda@nvda.groups.io>
Sent: Wednesday, July 04, 2018 4:28 AM
Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox


Hi
You can try this: https://saomaicenter.org/en/downloads
----------------
Dang Manh Cuong
The Assistive technology specialist
Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
Tel: +8428 7302-4488
E-mail: vanphong@...; congnghe@...
Facebook: https://www.facebook.com/saomaicenterfortheblind
Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org Mobile / Zalo: +84 902-572-300
E-mail: @cuongdang; cuong@...
Skype name: dangmanhcuong
facebook: http://facebook.com/dangmanhcuong
Twitter: @ManhCuongTech

----- Original Message -----
From: Joseph Lee
To: nvda@nvda.groups.io
Sent: Wednesday, July 04, 2018 10:07 AM
Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox


Hi,

Do you have an example website where we can try reproducing this? Thanks.

Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dang Manh Cuong
Sent: Tuesday, July 3, 2018 8:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] Cannot press c or shift+C to jump to combobox



To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in web page created using drupal. This also occurs when I use driver pack a program for searching driver. NVDA just sayy no comboboxes, but I can jump to it using tab or arrows. Seeing this problem with Firefox, Internet explorer, crhome and Microsoft edge.

I think this is not enough to create issue on gidhub so I share here, and I'll research more before submitting an issue. Hope you can pick time research this with me.
Cuong

----------------
Dang Manh Cuong
The Assistive technology specialist
Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
Tel: +8428 7302-4488
E-mail: vanphong@...; congnghe@...
Facebook: https://www.facebook.com/saomaicenterfortheblind
Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org Mobile / Zalo: +84 902-572-300
E-mail: @cuongdang; cuong@...
Skype name: dangmanhcuong
facebook: http://facebook.com/dangmanhcuong
Twitter: @ManhCuongTech


Re: FW: [nvda-translations] Changes to release process

Brian's Mail list account <bglists@...>
 

See my comments on the dev list, but to me the naming needs to be different
as many here use master as a working copy cos its stable this change will
dump them into the bleeding edge chain.
I'd propose doing away with master and keeping next instead, and yes I did
read the post but in reality changing a name is no different on one branch
than on another, then people who are on master will migrate to beta as they
become available staying on reasonably stable code. I can see tears before
bedtime otherwise when a bleeding edge update screws up somebody's working
copy who might not have read these messages on this list.
I think this makes more sense from the users point of view and does not mean
a master user has to do anything at all.
Comments?
Brian using logic for a change!

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

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda@groups.io>
Sent: Wednesday, July 04, 2018 3:13 AM
Subject: [nvda] FW: [nvda-translations] Changes to release process


Dear NVDA community,

Please read the updated release process document from NV Access (linked in the message below).

In short:
1. No more dedicated bleeding-edge next snapshots: what used to be next branch will now become master branch in the future.
2. A dedicated "beta" branch has been created on NVDA screen reader source code, used for stabilization work.
3. Approximately seven weeks before release of the next version, whichever stable code that is in master branch will be merged into the beta branch and will undergo two weeks of stabilization. This means you'll see increase in activity from beta branch around early January, early April, early July, and early October.
4. Around middle of January, April, July, and October, a beta build might be released. A series of beta builds are released, culminating in release candidate, and if no changes were made between the latest candidate in a week, a stable version will hit the air.

For users: many of you do not have to worry about this change, as majority of users are using stable releases.

For snapshot testers:
* If you are on next, you'll be moved to master branch when the new process takes effect.
* If you are on master, it'll be similar in nature to next snapshots of today.
* If you want to provide feedback on what is now master snapshots (beta builds in the future), please wait until the first beta for 2018.3 hits the air before switching to beta channel.
* Regardless of which branch you are using now (and master branch for everyone in the future, or perhaps beta builds), early feedback matters, so please do file them on GitHub (if you need to file an issue here, feel free to do so, and Quentin and/or another contributor will create a GitHub issue on your behalf).

For developers (especially for third parties writing new features): the following is a copy of my notes to be sent to the development list:

1. Please work from a topic branch: a topic branch is NOT your master branch - it is a separate branch that is forked from latest NV Access's master branch at the time you start your work, with commits sent to your fork of NVDA source code, not to NV Access directly yet.
2. Have a plan as you work: be sure to clearly define what you're working on, including data you need, debug plans, messages, impact and what not.
3. Test, test, test: just because your changes work for you doesn't mean it works for others, so be sure to test your work in various scenarios.
4. Run unit tests and other forms of tests: before committing your work (or submitting a pull request), be sure to run "scons tests" to really make sure your modifications does not break anything. This is important right before creating a pull request, as Appveyor will also run tests and will let you know if it breaks.
5. Document things: whenever you introduce a feature, document it in the user guide under appropriate section(s). Also, in case you're creating a brand new module in NVDA, please provide a short docstring (at the top of the file) explaining what your new module is, use cases and what not.
6. Help translators understand your message: if your work includes new messages, please do two things before submitting a pull request: make it translatable (unless justification is present), and accompany it with translator comments.
7. Keep up with others around the world: sometimes, a feature introduced by another person may (drastically) affect your work. This is the case especially if dependencies are changed, API changes occur and what not. Be sure to keep an eye on commits to NV Access's master branch, and if the change in there applies to your work, merge the master branch into your topic branch (not the other way around).
8. Do not be afraid to stand up to reviewers: during pull request discussion, you'll get feedback from reviewers (including NV Access people and others). If you believe the reviewer is having difficulty understanding your "intentions" (code edits), be prepared to provide a helpful explanation or two so you and the reviewer can be on the same page.
9. Approval != (not equal to) release: even with another person approving your feature, the world won't see it in action until NV Access approves your work and merges your pull request into master branch.
10. Test, test more, and test even more: just because your pull request is merged into master branch does not mean your work is over: it is just beginning. As user feedback comes in and based on follow-up tests, you might be asked to make changes to your work (or you can provide updates in the form of another pull request on your own).

Thanks.
Cheers,
Joseph


-----Original Message-----
From: nvda-translations@groups.io <nvda-translations@groups.io> On Behalf Of Michael Curran
Sent: Tuesday, July 3, 2018 6:43 PM
To: NVDA screen reader development <nvda-devel@...>; nvda-translations@groups.io
Subject: [nvda-translations] Changes to release process

Hi contributors,


We have made some small changes to the NVDA release process. Please read the updated Release Process article carefully to understand the changes and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be merged straight to master. Periodic betas will be offered startin from 5 weeks before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though technically, translations are now based on a new "beta" branch rather than master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


New release system and new snapshot names from Mick

Brian's Mail list account <bglists@...>
 

From: "Mick Curran" <mick@...>
To: "NVDA screen reader development" <nvda-devel@...>;
<nvda-translations@groups.io>
Sent: Wednesday, July 04, 2018 2:43 AM
Subject: [Nvda-devel] Changes to release process


Hi contributors,


We have made some small changes to the NVDA release process. Please read
the updated Release Process article carefully to understand the changes
and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be merged
straight to master. Periodic betas will be offered startin from 5 weeks
before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though
technically, translations are now based on a new "beta" branch rather than
master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Brian comments. I think this is actually going to affect people on this list
like myself who use the bleeding edge code as portable versions and master
as a daily working version.
I worry a little hear about a large number of untested by users items
arriving in the beta all at once which might be a little scary if a lot of
people find issues. At the moment they hit next regularly and one can see
the wood for the trees so to speak.

If you have any comments, send them to Mick not me though, as I do not see
any kind of consultation with users on this one.
Brian

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


Re: Cannot press c or shift+C to jump to combobox

 

Hi
----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech

----- Original Message -----
From: The Wolf
Sent: Wednesday, July 04, 2018 10:27 AM
Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox

where can I get the driver pack from so I can see if I am running in to the same problem you are?

On 7/3/2018 8:01 PM, Dang Manh Cuong wrote:
To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in web page created using drupal. This also occurs when I use driver pack  a program for searching driver. NVDA just sayy no comboboxes, but I can jump to it using tab or arrows. Seeing this problem with Firefox, Internet explorer, crhome and Microsoft edge.
I think this is not enough to create issue on gidhub so I share here, and I'll research more before submitting an issue. Hope you can pick time research this with me.
Cuong
----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech

-- 
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y


Re: Cannot press c or shift+C to jump to combobox

 

Hi,

Ah, the control in question is exposed as a list box, for which NVDA does not recognize as a combo box.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dang Manh Cuong
Sent: Tuesday, July 3, 2018 8:29 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox

 

Hi

----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech

----- Original Message -----

From: Joseph Lee

Sent: Wednesday, July 04, 2018 10:07 AM

Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox

 

Hi,

Do you have an example website where we can try reproducing this? Thanks.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dang Manh Cuong
Sent: Tuesday, July 3, 2018 8:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] Cannot press c or shift+C to jump to combobox

 

To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in web page created using drupal. This also occurs when I use driver pack  a program for searching driver. NVDA just sayy no comboboxes, but I can jump to it using tab or arrows. Seeing this problem with Firefox, Internet explorer, crhome and Microsoft edge.

I think this is not enough to create issue on gidhub so I share here, and I'll research more before submitting an issue. Hope you can pick time research this with me.
Cuong

----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech


Re: Cannot press c or shift+C to jump to combobox

 

Hi
----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech

----- Original Message -----
From: Joseph Lee
Sent: Wednesday, July 04, 2018 10:07 AM
Subject: Re: [nvda] Cannot press c or shift+C to jump to combobox

Hi,

Do you have an example website where we can try reproducing this? Thanks.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dang Manh Cuong
Sent: Tuesday, July 3, 2018 8:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] Cannot press c or shift+C to jump to combobox

 

To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in web page created using drupal. This also occurs when I use driver pack  a program for searching driver. NVDA just sayy no comboboxes, but I can jump to it using tab or arrows. Seeing this problem with Firefox, Internet explorer, crhome and Microsoft edge.

I think this is not enough to create issue on gidhub so I share here, and I'll research more before submitting an issue. Hope you can pick time research this with me.
Cuong

----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech


Re: Cannot press c or shift+C to jump to combobox

 

where can I get the driver pack from so I can see if I am running in to the same problem you are?

On 7/3/2018 8:01 PM, Dang Manh Cuong wrote:
To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in web page created using drupal. This also occurs when I use driver pack  a program for searching driver. NVDA just sayy no comboboxes, but I can jump to it using tab or arrows. Seeing this problem with Firefox, Internet explorer, crhome and Microsoft edge.
I think this is not enough to create issue on gidhub so I share here, and I'll research more before submitting an issue. Hope you can pick time research this with me.
Cuong
----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech

-- 
check out my song on youtube
https://youtu.be/YeWgx2LRu7Y


Re: Cannot press c or shift+C to jump to combobox

 

Hi,

Do you have an example website where we can try reproducing this? Thanks.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Dang Manh Cuong
Sent: Tuesday, July 3, 2018 8:02 PM
To: nvda@nvda.groups.io
Subject: [nvda] Cannot press c or shift+C to jump to combobox

 

To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in web page created using drupal. This also occurs when I use driver pack  a program for searching driver. NVDA just sayy no comboboxes, but I can jump to it using tab or arrows. Seeing this problem with Firefox, Internet explorer, crhome and Microsoft edge.

I think this is not enough to create issue on gidhub so I share here, and I'll research more before submitting an issue. Hope you can pick time research this with me.
Cuong

----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech


Cannot press c or shift+C to jump to combobox

 

To all listers
Using NVDA 2018.2.1, and cannot press C or shift+C to jump to a combobox in web page created using drupal. This also occurs when I use driver pack  a program for searching driver. NVDA just sayy no comboboxes, but I can jump to it using tab or arrows. Seeing this problem with Firefox, Internet explorer, crhome and Microsoft edge.
I think this is not enough to create issue on gidhub so I share here, and I'll research more before submitting an issue. Hope you can pick time research this with me.
Cuong
----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech


Re: a question about recording with audacity

Bobby Vinton
 

Sounds very good.  Well I just tried that and it worked very well.  I wish I could have found a pod cast on this topic.

On 7/3/2018 9:19 PM, Dang Manh Cuong wrote:
Hi
other members gave good idiea, but if you still wanna try with Audacity, in the preferences (ctrl+P), at the devices category, tab to the interface host and choose windows wasapi, then tab the the recording device,  you'll see something like your device name + loopback at the combobox. Selecting this will make you able to record all thing you hear on speaker so you can record both of your voice and screen reader together. However, you must apply compressor afterr recording to make your voice and your screen reader level nearlyy the same volume.
Cuong
----------------
Dang Manh Cuong
The Assistive technology specialist
Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
Tel: +8428 7302-4488
E-mail: vanphong@...; congnghe@...
Facebook: https://www.facebook.com/saomaicenterfortheblind
Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
E-mail: @cuongdang; cuong@...
Skype name: dangmanhcuong
facebook: http://facebook.com/dangmanhcuong
Twitter: @ManhCuongTech

----- Original Message ----- From: "Bobby Vinton" <vinton.bobby5277@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, July 03, 2018 11:56 PM
Subject: Re: [nvda] a question about recording with audacity


Yes the usb microphone has it's own sound card. I can hear my screen reader very well butt my voice is very low. I want to put them together at the same volume.


On 7/3/2018 12:51 PM, Dang Manh Cuong wrote:
Hi Bobby
Does your microphone has it own sound card? If so, do you able to hear your voice through the sound card?
May be I could give advise afterr getting your reply.
Cuong
----------------
Dang Manh Cuong
The Assistive technology specialist
Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
Tel: +8428 7302-4488
E-mail: vanphong@...; congnghe@...
Facebook: https://www.facebook.com/saomaicenterfortheblind
Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org Mobile / Zalo: +84 902-572-300
E-mail: @cuongdang; cuong@...
Skype name: dangmanhcuong
facebook: http://facebook.com/dangmanhcuong
Twitter: @ManhCuongTech

----- Original Message ----- From: "Bobby Vinton" <vinton.bobby5277@...>
To: <nvda@groups.io>
Sent: Tuesday, July 03, 2018 10:20 PM
Subject: [nvda] a question about recording with audacity


Hay I have a usb microphone and would like to record my voice and screen reader together with audacity. I was wondering how this can be done? If any one knows just let me know.








FW: [nvda-translations] Changes to release process

 

Dear NVDA community,

Please read the updated release process document from NV Access (linked in the message below).

In short:
1. No more dedicated bleeding-edge next snapshots: what used to be next branch will now become master branch in the future.
2. A dedicated "beta" branch has been created on NVDA screen reader source code, used for stabilization work.
3. Approximately seven weeks before release of the next version, whichever stable code that is in master branch will be merged into the beta branch and will undergo two weeks of stabilization. This means you'll see increase in activity from beta branch around early January, early April, early July, and early October.
4. Around middle of January, April, July, and October, a beta build might be released. A series of beta builds are released, culminating in release candidate, and if no changes were made between the latest candidate in a week, a stable version will hit the air.

For users: many of you do not have to worry about this change, as majority of users are using stable releases.

For snapshot testers:
* If you are on next, you'll be moved to master branch when the new process takes effect.
* If you are on master, it'll be similar in nature to next snapshots of today.
* If you want to provide feedback on what is now master snapshots (beta builds in the future), please wait until the first beta for 2018.3 hits the air before switching to beta channel.
* Regardless of which branch you are using now (and master branch for everyone in the future, or perhaps beta builds), early feedback matters, so please do file them on GitHub (if you need to file an issue here, feel free to do so, and Quentin and/or another contributor will create a GitHub issue on your behalf).

For developers (especially for third parties writing new features): the following is a copy of my notes to be sent to the development list:

1. Please work from a topic branch: a topic branch is NOT your master branch - it is a separate branch that is forked from latest NV Access's master branch at the time you start your work, with commits sent to your fork of NVDA source code, not to NV Access directly yet.
2. Have a plan as you work: be sure to clearly define what you're working on, including data you need, debug plans, messages, impact and what not.
3. Test, test, test: just because your changes work for you doesn't mean it works for others, so be sure to test your work in various scenarios.
4. Run unit tests and other forms of tests: before committing your work (or submitting a pull request), be sure to run "scons tests" to really make sure your modifications does not break anything. This is important right before creating a pull request, as Appveyor will also run tests and will let you know if it breaks.
5. Document things: whenever you introduce a feature, document it in the user guide under appropriate section(s). Also, in case you're creating a brand new module in NVDA, please provide a short docstring (at the top of the file) explaining what your new module is, use cases and what not.
6. Help translators understand your message: if your work includes new messages, please do two things before submitting a pull request: make it translatable (unless justification is present), and accompany it with translator comments.
7. Keep up with others around the world: sometimes, a feature introduced by another person may (drastically) affect your work. This is the case especially if dependencies are changed, API changes occur and what not. Be sure to keep an eye on commits to NV Access's master branch, and if the change in there applies to your work, merge the master branch into your topic branch (not the other way around).
8. Do not be afraid to stand up to reviewers: during pull request discussion, you'll get feedback from reviewers (including NV Access people and others). If you believe the reviewer is having difficulty understanding your "intentions" (code edits), be prepared to provide a helpful explanation or two so you and the reviewer can be on the same page.
9. Approval != (not equal to) release: even with another person approving your feature, the world won't see it in action until NV Access approves your work and merges your pull request into master branch.
10. Test, test more, and test even more: just because your pull request is merged into master branch does not mean your work is over: it is just beginning. As user feedback comes in and based on follow-up tests, you might be asked to make changes to your work (or you can provide updates in the form of another pull request on your own).

Thanks.
Cheers,
Joseph

-----Original Message-----
From: nvda-translations@groups.io <nvda-translations@groups.io> On Behalf Of Michael Curran
Sent: Tuesday, July 3, 2018 6:43 PM
To: NVDA screen reader development <nvda-devel@...>; nvda-translations@groups.io
Subject: [nvda-translations] Changes to release process

Hi contributors,


We have made some small changes to the NVDA release process. Please read the updated Release Process article carefully to understand the changes and how they will affect you.

https://github.com/nvaccess/nvda/wiki/ReleaseProcess


In short, Next/incubation is going away, and prs are going to be merged straight to master. Periodic betas will be offered startin from 5 weeks before a release.

Please read the entire article to understand the changes fully.


Translators should not be directly affected by this change. Though technically, translations are now based on a new "beta" branch rather than master.


Mick









--
--
Mick Curran
Executive Director, NV Access Limited
PH: +61 7 3149 3306 ext. 101
www: http://www.nvaccess.org/
Twitter: @NVAccess
Facebook: http://www.facebook.com/NVAccess