Date   

reminders in outlook

Jessica D
 

Hi,

I have a few reminders that keep coming up in Outlook.

I’m using office 365.

It’s outlook 2016.

I can’t dismiss these reminders.

What can I do to fix this?

 

Thanks,

Jessica

 

Sent from Mail for Windows 10

 


Re: Github

Cearbhall O'Meadhra
 

Quentin,

 

I tried again, this time with Google Chrome. It worked fine! So, the problem is with Firefox and NVDA.  The NVDA log shows nothing for the Firefox action except innocent keystrokes but the upload action seems to be blocked in Firefox.

 

Anyway, it does work with Google Chrome.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Wednesday, September 6, 2017 12:22 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Github

 

Odd, it seems to be working for me.  Can anyone else reproduce this problem?

 

 

Press TAB four times to get to the Browse button and then press spacebar or enter to activate it.  It should bring up a standard Windows file open dialog.

 

Otherwise, the only thing I can think of, is whether you had explorer crashed or busy in the background or something?

 

Regards


Quentin.

 

On Wed, Sep 6, 2017 at 6:17 PM, Brian's Mail list account via Groups.Io <bglists@...> wrote:

It did not work in firefox either, I think short fragments of the log in the body are OK its other files that you really need to attach in case they get corrupted.
It seems to me that the browse, um does not browse ..!
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sarah k Alawami" <marrie12@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github


How odd. What shoudl happen si syou hit brows and the file dialogue shoudl appear, it does under safari. Try chrome maybe and see if that works and or firefox or edge?

Good luck.

On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra <cearbhall.omeadhra@...> wrote:

Quentin,

Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather than simply pasting in the contents of the log file, for instance . The problem is that I cannot get any option to attach a file when I clicked on the “browse” button. It would be a great help if you could explain how to attach a file using NVDA.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@... <mailto:cearbhall.omeadhra@...>




From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>] On Behalf Of Quentin Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or generally report something that isn't working / could work better / should be implemented etc, what you want to do is create a new issue.  The link to the issues section is https://github.com/nvaccess/nvda/issues <https://github.com/nvaccess/nvda/issues>

Unless you are writing code yourself, you can mostly ignore the other sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to search for the issue you want to report.  (the first one searches code and other things, you want to search issues).  So, if someone reported a problem with footnotes in Word 2016 for instance, I'd search for "word 2016 footnotes" or similar in that second edit box.  There are two types of issues, open and closed. Open issues are either new issues that haven't been triaged yet (that is, no one has looked at them to see how serious they are, whether the issue has already been reported etc), or issues which are being worked on, or waiting to be worked on.  Closed issues are issues which have either been fixed, or which are duplicates of other issues, or sometimes things which can't or won't be fixed.  If the problem with footnotes is that you want them to appear at the top of the page for instance, then that isn't something related to NVDA.  That's a feature request for Word itself and you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump straight there with https://github.com/nvaccess/nvda/issues/new <https://github.com/nvaccess/nvda/issues/new>

When you create a new issue, there is a block of text in the "comment" prompting you for the kinds of information that are useful in diagnosing the issue.  Please try and include: steps to reproduce the issue, attach any files which might help (eg if Word crashes every time you try and check formatting in this particular file, if you can share it, that would help), what should happen and what actually happens, and your system configuration (Windows version, application version, NVDA version and whether installed or portable), and anything you've done to try and resolve or get more information (eg tried different version of NVDA or other program).  Don't stress if you don't have every piece of that information or if you aren't sure if the issue has been filed before. When someone goes to triage the issue, they will ask for more information if needed.  If the issue has been filed previously, they will link to it (and likely close the duplicate issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@... <mailto:linomorales001@...>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing as heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site.  I haven't signed up yet but it looks easy to do so and to create a pull request, which I assume is what is generally referred to on this list as a ticket.  But many people may find the page confusing. Is there a way that some sort of short help information can be inserted after the navigation links on the page, instructing people what to do to create what are called tickets, perhaps also how to search for tickets and how to create an account?  If tickets are desired from the widest variety of users, this process should be somehow explained and done so in a place that those wishing to create tickets will be likely to see the explanation.

Gene




--
Quentin Christensen
Training and Support Manager

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

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







 

--

Quentin Christensen
Training and Support Manager

 

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

 

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


Re: Github

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

I'll check again later, it seemed to hang everything the last time I did it on windows 7.
Brian

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

----- Original Message -----
From: "Quentin Christensen" <quentin@nvaccess.org>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 12:22 PM
Subject: Re: [nvda] Github


Odd, it seems to be working for me. Can anyone else reproduce this problem?

Easiest way is to go to: https://github.com/nvaccess/nvda/issues/new

Press TAB four times to get to the Browse button and then press spacebar or
enter to activate it. It should bring up a standard Windows file open
dialog.

Otherwise, the only thing I can think of, is whether you had explorer
crashed or busy in the background or something?

Regards

Quentin.

On Wed, Sep 6, 2017 at 6:17 PM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

It did not work in firefox either, I think short fragments of the log in
the body are OK its other files that you really need to attach in case they
get corrupted.
It seems to me that the browse, um does not browse ..!
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sarah k Alawami" <marrie12@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github


How odd. What shoudl happen si syou hit brows and the file dialogue shoudl
appear, it does under safari. Try chrome maybe and see if that works and or
firefox or edge?

Good luck.

On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra <
cearbhall.omeadhra@blbc.ie> wrote:

Quentin,

Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather
than simply pasting in the contents of the log file, for instance . The
problem is that I cannot get any option to attach a file when I clicked on
the “browse” button. It would be a great help if you could explain how to
attach a file using NVDA.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie
<mailto:cearbhall.omeadhra@blbc.ie>




From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:
nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>] On Behalf Of Quentin
Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or
generally report something that isn't working / could work better / should
be implemented etc, what you want to do is create a new issue. The link to
the issues section is https://github.com/nvaccess/nvda/issues <
https://github.com/nvaccess/nvda/issues>

Unless you are writing code yourself, you can mostly ignore the other
sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to search
for the issue you want to report. (the first one searches code and other
things, you want to search issues). So, if someone reported a problem with
footnotes in Word 2016 for instance, I'd search for "word 2016 footnotes"
or similar in that second edit box. There are two types of issues, open
and closed. Open issues are either new issues that haven't been triaged yet
(that is, no one has looked at them to see how serious they are, whether
the issue has already been reported etc), or issues which are being worked
on, or waiting to be worked on. Closed issues are issues which have either
been fixed, or which are duplicates of other issues, or sometimes things
which can't or won't be fixed. If the problem with footnotes is that you
want them to appear at the top of the page for instance, then that isn't
something related to NVDA. That's a feature request for Word itself and
you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump
straight there with https://github.com/nvaccess/nvda/issues/new <
https://github.com/nvaccess/nvda/issues/new>

When you create a new issue, there is a block of text in the "comment"
prompting you for the kinds of information that are useful in diagnosing
the issue. Please try and include: steps to reproduce the issue, attach
any files which might help (eg if Word crashes every time you try and check
formatting in this particular file, if you can share it, that would help),
what should happen and what actually happens, and your system configuration
(Windows version, application version, NVDA version and whether installed
or portable), and anything you've done to try and resolve or get more
information (eg tried different version of NVDA or other program). Don't
stress if you don't have every piece of that information or if you aren't
sure if the issue has been filed before. When someone goes to triage the
issue, they will ask for more information if needed. If the issue has been
filed previously, they will link to it (and likely close the duplicate
issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@gmail.com
<mailto:linomorales001@gmail.com>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing as
heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site. I haven't signed up
yet but it looks easy to do so and to create a pull request, which I assume
is what is generally referred to on this list as a ticket. But many people
may find the page confusing. Is there a way that some sort of short help
information can be inserted after the navigation links on the page,
instructing people what to do to create what are called tickets, perhaps
also how to search for tickets and how to create an account? If tickets
are desired from the widest variety of users, this process should be
somehow explained and done so in a place that those wishing to create
tickets will be likely to see the explanation.

Gene




--
Quentin Christensen
Training and Support Manager

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

www.nvaccess.org <http://www.nvaccess.org/>
Facebook: http://www.facebook.com/NVAccess <http://www.facebook.com/NVAcc
ess>
Twitter: @NVAccess





--
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


Re: NVDA constantly repeating icons on the desktop

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

Yes but the eternal question is how. I could understand it if this person had an animated wallpaper or some animated icon, but otherwise its a bit of mystery.
I well remember a spoof virus you could 'infect windows users with that had a sheep called Dolly wandering about the desktop eating icons. Of course it was not really doing any harm as such, as it was just a wscreensaver that took a snap of the current desktop put up that screen and had Dolly munch the icons on the picture.
Bit wasted on the blind though.
Brian

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

----- Original Message -----
From: "Chris" <chrismedley@btinternet.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 1:10 PM
Subject: Re: [nvda] NVDA constantly repeating icons on the desktop


Probably because the screen is being refreshed that can cause it to do this
Hit F5 On the desktop to simulate this


Re: Github

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

Yes but your own comments do not come back to you, which seems an odd way of working to me.
Brian

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

----- Original Message -----
From: "zahra" <nasrinkhaksar3@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 3:03 PM
Subject: Re: [nvda] Github


hi gene, bhavya, quentin, brian and all.

i subscribed to nvda github and reported my bugs and also suggestions.
when i send comment, i am subscribed to recieve notification.
even i can subscribed to recieve notifications (for example for new
comments) without sending comment.
i recieve new comments from developers and users.
God bless you all.

On 9/6/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Odd, it seems to be working for me. Can anyone else reproduce this
problem?

Easiest way is to go to: https://github.com/nvaccess/nvda/issues/new

Press TAB four times to get to the Browse button and then press spacebar or
enter to activate it. It should bring up a standard Windows file open
dialog.

Otherwise, the only thing I can think of, is whether you had explorer
crashed or busy in the background or something?

Regards

Quentin.

On Wed, Sep 6, 2017 at 6:17 PM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

It did not work in firefox either, I think short fragments of the log in
the body are OK its other files that you really need to attach in case
they
get corrupted.
It seems to me that the browse, um does not browse ..!
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sarah k Alawami" <marrie12@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github


How odd. What shoudl happen si syou hit brows and the file dialogue
shoudl
appear, it does under safari. Try chrome maybe and see if that works and
or
firefox or edge?

Good luck.

On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra <
cearbhall.omeadhra@blbc.ie> wrote:

Quentin,

Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather
than simply pasting in the contents of the log file, for instance . The
problem is that I cannot get any option to attach a file when I clicked
on
the “browse” button. It would be a great help if you could explain how
to
attach a file using NVDA.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie
<mailto:cearbhall.omeadhra@blbc.ie>




From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:
nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>] On Behalf Of Quentin
Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or
generally report something that isn't working / could work better /
should
be implemented etc, what you want to do is create a new issue. The link
to
the issues section is https://github.com/nvaccess/nvda/issues <
https://github.com/nvaccess/nvda/issues>

Unless you are writing code yourself, you can mostly ignore the other
sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to
search
for the issue you want to report. (the first one searches code and
other
things, you want to search issues). So, if someone reported a problem
with
footnotes in Word 2016 for instance, I'd search for "word 2016
footnotes"
or similar in that second edit box. There are two types of issues, open
and closed. Open issues are either new issues that haven't been triaged
yet
(that is, no one has looked at them to see how serious they are, whether
the issue has already been reported etc), or issues which are being
worked
on, or waiting to be worked on. Closed issues are issues which have
either
been fixed, or which are duplicates of other issues, or sometimes things
which can't or won't be fixed. If the problem with footnotes is that
you
want them to appear at the top of the page for instance, then that isn't
something related to NVDA. That's a feature request for Word itself and
you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump
straight there with https://github.com/nvaccess/nvda/issues/new <
https://github.com/nvaccess/nvda/issues/new>

When you create a new issue, there is a block of text in the "comment"
prompting you for the kinds of information that are useful in diagnosing
the issue. Please try and include: steps to reproduce the issue, attach
any files which might help (eg if Word crashes every time you try and
check
formatting in this particular file, if you can share it, that would
help),
what should happen and what actually happens, and your system
configuration
(Windows version, application version, NVDA version and whether
installed
or portable), and anything you've done to try and resolve or get more
information (eg tried different version of NVDA or other program).
Don't
stress if you don't have every piece of that information or if you
aren't
sure if the issue has been filed before. When someone goes to triage the
issue, they will ask for more information if needed. If the issue has
been
filed previously, they will link to it (and likely close the duplicate
issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@gmail.com
<mailto:linomorales001@gmail.com>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing
as
heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site. I haven't signed up
yet but it looks easy to do so and to create a pull request, which I
assume
is what is generally referred to on this list as a ticket. But many
people
may find the page confusing. Is there a way that some sort of short help
information can be inserted after the navigation links on the page,
instructing people what to do to create what are called tickets, perhaps
also how to search for tickets and how to create an account? If tickets
are desired from the widest variety of users, this process should be
somehow explained and done so in a place that those wishing to create
tickets will be likely to see the explanation.

Gene




--
Quentin Christensen
Training and Support Manager

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

www.nvaccess.org <http://www.nvaccess.org/>
Facebook: http://www.facebook.com/NVAccess
<http://www.facebook.com/NVAcc
ess>
Twitter: @NVAccess





--
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

--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


Re: Github

Cearbhall O'Meadhra
 

Quentin,

 

I went to the link you supplied below, logged in and then found the browse button as you suggested. That did, indeed, open up the usual file search dialog. I found the log file that I want to upload and pressed open on that file. The dialog closed and I was returned to the new issue screen with a message 2no files selected.

Just for the record, I am using windows 10, NVDA 2017.3 and Mozilla Firefox all latest updates.

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Wednesday, September 6, 2017 12:22 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Github

 

Odd, it seems to be working for me.  Can anyone else reproduce this problem?

 

 

Press TAB four times to get to the Browse button and then press spacebar or enter to activate it.  It should bring up a standard Windows file open dialog.

 

Otherwise, the only thing I can think of, is whether you had explorer crashed or busy in the background or something?

 

Regards


Quentin.

 

On Wed, Sep 6, 2017 at 6:17 PM, Brian's Mail list account via Groups.Io <bglists@...> wrote:

It did not work in firefox either, I think short fragments of the log in the body are OK its other files that you really need to attach in case they get corrupted.
It seems to me that the browse, um does not browse ..!
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sarah k Alawami" <marrie12@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github


How odd. What shoudl happen si syou hit brows and the file dialogue shoudl appear, it does under safari. Try chrome maybe and see if that works and or firefox or edge?

Good luck.

On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra <cearbhall.omeadhra@...> wrote:

Quentin,

Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather than simply pasting in the contents of the log file, for instance . The problem is that I cannot get any option to attach a file when I clicked on the “browse” button. It would be a great help if you could explain how to attach a file using NVDA.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@... <mailto:cearbhall.omeadhra@...>




From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>] On Behalf Of Quentin Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or generally report something that isn't working / could work better / should be implemented etc, what you want to do is create a new issue.  The link to the issues section is https://github.com/nvaccess/nvda/issues <https://github.com/nvaccess/nvda/issues>

Unless you are writing code yourself, you can mostly ignore the other sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to search for the issue you want to report.  (the first one searches code and other things, you want to search issues).  So, if someone reported a problem with footnotes in Word 2016 for instance, I'd search for "word 2016 footnotes" or similar in that second edit box.  There are two types of issues, open and closed. Open issues are either new issues that haven't been triaged yet (that is, no one has looked at them to see how serious they are, whether the issue has already been reported etc), or issues which are being worked on, or waiting to be worked on.  Closed issues are issues which have either been fixed, or which are duplicates of other issues, or sometimes things which can't or won't be fixed.  If the problem with footnotes is that you want them to appear at the top of the page for instance, then that isn't something related to NVDA.  That's a feature request for Word itself and you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump straight there with https://github.com/nvaccess/nvda/issues/new <https://github.com/nvaccess/nvda/issues/new>

When you create a new issue, there is a block of text in the "comment" prompting you for the kinds of information that are useful in diagnosing the issue.  Please try and include: steps to reproduce the issue, attach any files which might help (eg if Word crashes every time you try and check formatting in this particular file, if you can share it, that would help), what should happen and what actually happens, and your system configuration (Windows version, application version, NVDA version and whether installed or portable), and anything you've done to try and resolve or get more information (eg tried different version of NVDA or other program).  Don't stress if you don't have every piece of that information or if you aren't sure if the issue has been filed before. When someone goes to triage the issue, they will ask for more information if needed.  If the issue has been filed previously, they will link to it (and likely close the duplicate issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@... <mailto:linomorales001@...>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing as heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site.  I haven't signed up yet but it looks easy to do so and to create a pull request, which I assume is what is generally referred to on this list as a ticket.  But many people may find the page confusing. Is there a way that some sort of short help information can be inserted after the navigation links on the page, instructing people what to do to create what are called tickets, perhaps also how to search for tickets and how to create an account?  If tickets are desired from the widest variety of users, this process should be somehow explained and done so in a place that those wishing to create tickets will be likely to see the explanation.

Gene




--
Quentin Christensen
Training and Support Manager

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

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







 

--

Quentin Christensen
Training and Support Manager

 

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

 

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


Re: New NVDA sounds

 

quentin.
can you please send me the new sound privately?
thanks so much and God bless you.

On 9/6/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Mostly just to back up what others have said and give a bit more
background. Initially, the idea was simply to "refresh" the sounds, much
like we have also done with the logo in 2017.3. It wasn't that nobody
liked them, but it was really split - there were people who preferred the
old sounds, some who liked the new sounds, and some who wanted to change
the sounds, but didn't like the new ones either. We hadn't considered that
until the feedback started coming in from the snapshot users. We realised
then that what we needed to implement, more than just a new set of sounds
on its own, was a way for people to be able to change their own sounds.
One idea for this is along the lines of the way you can install add-ons.
Ideally, unlike add-ons, we want something that will be a bit easier for
users to package without needing programming skills.

Because of the divided feedback, we decided the best option (since it
hadn't yet rolled out to the majority of users), was to pull the new sounds
while we work on this new sound "theme" feature.

So, that's where it's at currently, and I believe someone else has provided
instructions in this thread for your question. Note that if you do that,
keep a backup of the sounds as they may get overridden when you update
NVDA, and they'll be easier to swap back if you've got the files handy.

Regards

Quentin.

On Wed, Sep 6, 2017 at 9:37 AM, Christopher-Mark Gilland <
clgilland07@gmail.com> wrote:

Guys,

I was running, a while back a snapshot of NVDA 2017.3, and noticed that
the NVDA sounds for things like startup, quitting, etc. were different
than
what they have been for the longest time.

Now, with the official release of 2017.3, I'm not seeing this.

Can someone advise me on how to go about getting those other sounds? I
liked them much better.

Chris.
---
Christopher Gilland
Co-founder of Genuine Safe Haven Ministries

http://www.gshministry.org
(980) 500-9575



--
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
--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


Thunderbird Add On To Allow First Letter Navigation For Folders

Ron Canazzi
 

As per request: here is the message containing information about the quick key navigation add on for Thunderbird and how to obtain it. It works like a charm.




-------- Forwarded Message --------
Subject: [nvda] Thunderbird Add On To Allow First Letter Navigation For Folders
Date: Wed, 2 Aug 2017 01:29:24 -0400
From: Ron Canazzi <aa2vm@...>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io


Hi Group,


I got this referenced from another list.

There is an  add on that allows folder navigation by typing the first 
letter and it is called 'quick key folder navigation.'  The description 
says you have to type the first 3 letters, but if you only have one 
folder that begins with the letter key you press, then you will move 
right to the folder with just the first key press. I have installed this 
and it works great.  This restores one of the favorite features for 
screen reader users that existed in the venerable and now largely 
defunct Outlook Express.


Using Thunderbird, it is easy to install this add on.  Just click 
tools/add on manager/search for add on.  Type in quick folder key 
navigation, press enter, then tab to the list of results, highlight the 
add on, right click and choose install.  Then follow the prompts.  There 
is no need to browse the Mozilla website for the add on.


-- 
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: thunderbird add on

Gene
 

A google search for Thunderbird add on first letter navigation produced this page as the second result
 
Gene

----- Original Message -----
From: Don H
Sent: Wednesday, September 06, 2017 7:40 AM
Subject: [nvda] thunderbird add on

A short while ago someone on the list recommended a Thunderbird add on
that allowed single letter navigation of the folder tree in
Thunderbird.  Can someone give the name of that add on again.

Thanks





Re: Github

 

hi gene, bhavya, quentin, brian and all.

i subscribed to nvda github and reported my bugs and also suggestions.
when i send comment, i am subscribed to recieve notification.
even i can subscribed to recieve notifications (for example for new
comments) without sending comment.
i recieve new comments from developers and users.
God bless you all.

On 9/6/17, Quentin Christensen <quentin@nvaccess.org> wrote:
Odd, it seems to be working for me. Can anyone else reproduce this
problem?

Easiest way is to go to: https://github.com/nvaccess/nvda/issues/new

Press TAB four times to get to the Browse button and then press spacebar or
enter to activate it. It should bring up a standard Windows file open
dialog.

Otherwise, the only thing I can think of, is whether you had explorer
crashed or busy in the background or something?

Regards

Quentin.

On Wed, Sep 6, 2017 at 6:17 PM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

It did not work in firefox either, I think short fragments of the log in
the body are OK its other files that you really need to attach in case
they
get corrupted.
It seems to me that the browse, um does not browse ..!
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sarah k Alawami" <marrie12@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github


How odd. What shoudl happen si syou hit brows and the file dialogue
shoudl
appear, it does under safari. Try chrome maybe and see if that works and
or
firefox or edge?

Good luck.

On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra <
cearbhall.omeadhra@blbc.ie> wrote:

Quentin,

Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather
than simply pasting in the contents of the log file, for instance . The
problem is that I cannot get any option to attach a file when I clicked
on
the “browse” button. It would be a great help if you could explain how
to
attach a file using NVDA.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie
<mailto:cearbhall.omeadhra@blbc.ie>




From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:
nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>] On Behalf Of Quentin
Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or
generally report something that isn't working / could work better /
should
be implemented etc, what you want to do is create a new issue. The link
to
the issues section is https://github.com/nvaccess/nvda/issues <
https://github.com/nvaccess/nvda/issues>

Unless you are writing code yourself, you can mostly ignore the other
sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to
search
for the issue you want to report. (the first one searches code and
other
things, you want to search issues). So, if someone reported a problem
with
footnotes in Word 2016 for instance, I'd search for "word 2016
footnotes"
or similar in that second edit box. There are two types of issues, open
and closed. Open issues are either new issues that haven't been triaged
yet
(that is, no one has looked at them to see how serious they are, whether
the issue has already been reported etc), or issues which are being
worked
on, or waiting to be worked on. Closed issues are issues which have
either
been fixed, or which are duplicates of other issues, or sometimes things
which can't or won't be fixed. If the problem with footnotes is that
you
want them to appear at the top of the page for instance, then that isn't
something related to NVDA. That's a feature request for Word itself and
you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump
straight there with https://github.com/nvaccess/nvda/issues/new <
https://github.com/nvaccess/nvda/issues/new>

When you create a new issue, there is a block of text in the "comment"
prompting you for the kinds of information that are useful in diagnosing
the issue. Please try and include: steps to reproduce the issue, attach
any files which might help (eg if Word crashes every time you try and
check
formatting in this particular file, if you can share it, that would
help),
what should happen and what actually happens, and your system
configuration
(Windows version, application version, NVDA version and whether
installed
or portable), and anything you've done to try and resolve or get more
information (eg tried different version of NVDA or other program).
Don't
stress if you don't have every piece of that information or if you
aren't
sure if the issue has been filed before. When someone goes to triage the
issue, they will ask for more information if needed. If the issue has
been
filed previously, they will link to it (and likely close the duplicate
issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@gmail.com
<mailto:linomorales001@gmail.com>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing
as
heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site. I haven't signed up
yet but it looks easy to do so and to create a pull request, which I
assume
is what is generally referred to on this list as a ticket. But many
people
may find the page confusing. Is there a way that some sort of short help
information can be inserted after the navigation links on the page,
instructing people what to do to create what are called tickets, perhaps
also how to search for tickets and how to create an account? If tickets
are desired from the widest variety of users, this process should be
somehow explained and done so in a place that those wishing to create
tickets will be likely to see the explanation.

Gene




--
Quentin Christensen
Training and Support Manager

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

www.nvaccess.org <http://www.nvaccess.org/>
Facebook: http://www.facebook.com/NVAccess
<http://www.facebook.com/NVAcc
ess>
Twitter: @NVAccess





--
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
--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org


Re: Unable to Install NVDA 17.3 on HP laptop

Hicks Steven (CORNWALL IT SERVICES) <steven.hicks@...>
 

User account control, go in to control panel and search for user?

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Akbar S. Currim
Sent: 06 September 2017 07:56
To: nvda@nvda.groups.io
Subject: Re: [nvda] Unable to Install NVDA 17.3 on HP laptop

What is UAC and how do I change the level of the settings.
Thanks,

Akbar


On 9/6/17, Chris Wright via Groups.Io <blindgamer87=yahoo.com@groups.io> wrote:
If I remember correctly, portable and temporary copies of NVDA are
unable to interact with UAC. When you hear the UAC sound, press Alt+Y.
This should allow the installation to continue. Alternatively, you
could set the UAC notification level to 0 which prevents the prompt
from appearing and allows the software to run normally.
On Sep 5, 2017, at 11:52 PM, Lino Morales <linomorales001@gmail.com>
wrote:

Must been the UAC. It should have read it.


On 9/5/2017 11:22 AM, Akbar S. Currim wrote:
You are brilliant. Being unable to install even from a portable
copy I asked my sighted son to take a look at it. Apparently a
window was opening which was completely inaccessible which was
asking to confirm to allow to install the programme which I was not
aware of. When he (my son) clicked to allow it and then the
installation went through without a hitch.

Thanks to all and sorry for the bother.

Akbar


On 9/2/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
It could just be that something like an anti virus has updated
since the old

install and also it could be that new code in the latest nvda is
only now falling foul of malware filtering. Normally such programs
would tell you though, unless its a message which is inaccessible
of course.

It would really need a sighted person with hands on the machine to
solve it

I think. Its going to be something really annoyingly simple I'm sure.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "nasrin khaksar" <nasrinkhaksar3@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Friday, September 01, 2017 3:26 PM
Subject: Re: [nvda] Unable to Install NVDA 17.3 on HP laptop


hello.
did you try nvda without eloquence?
by default, it only has espeak and i dont think that the problem
relates to eloquence.

also, system requirements for nvda 17.2 and 17.3 are the same.


On 9/1/17, Akbar S. Currim <raahzam@gmail.com> wrote:
The Eloquence which I have is quite recent and it is also
installed on my second laptop on which I had no problem updating.
The "alt-tab"
method has tried by me several times and makes no difference.
Besides, when the updated version of NVDA finishes downloading it
automatically says that the download is complete and it will now
update the existing version of NVDA. with the negative result
already explained So I think I will just go ahead and make a
portable version from my proper working NVDA from my second
laptop and install it from there. I have not had any time as yet
to do that but maybe I will get down to doing it over the
weekend.
Thanks,
Akbar



On 9/1/17, Gene <gsasner@ripco.com> wrote:
I said entity because I have no idea who owns it now. It's
probably a company but since I didn't know, I said entity.

Gene


From: Brian's Mail list account via Groups.Io
Sent: Thursday, August 31, 2017 1:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Unable to Install NVDA 17.3 on HP laptop


Well entity?
It sounds exactly like it even to the lisp!
I got mine on an old cd called Home Page reader by IBM it was a
freebie.
Goes back a very long way!

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:- briang1@blueyonder.co.uk,
putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 31, 2017 12:12 PM
Subject: Re: [nvda] Unable to Install NVDA 17.3 on HP laptop


Via Voice isn't Eloquence. it is similar in sound and
performance, but it isn't the same program and isn't owned by
the same entity.

Gene
----- Original Message -----

From: Brian's Mail list account via Groups.Io
Sent: Thursday, August 31, 2017 5:05 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Unable to Install NVDA 17.3 on HP laptop


I've not noticed this on any of the legal Eloquence drivers,
even the old sapi 4 one called via voice. I agree that old
hacked one was rubbish but anyone using that still would
probably have no hair left by now.
smiley.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:- briang1@blueyonder.co.uk,
putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Austin Pinto" <austinpinto.xaviers@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 31, 2017 9:05 AM
Subject: Re: [nvda] Unable to Install NVDA 17.3 on HP laptop


hi.
this may be caused by an old version of elequence.
before you update switch to espeak then upgrade and then switch
back.
also do a restart of your laptop.
i dont mean shutdown and restart.
i mean a full restart.

On 8/31/17, Shaun Everiss <sm.everiss@gmail.com> wrote:
Hmmm did you try to alt tab a few times.

Sometimes I get a uac prompt, usually it pops up but if I for
example have more than a couple windows open then it may be
hidden.

The trick is to know how long something should take to
download and if you heard the completed sound or think it
should be well should be, then you need to alt tab.

On the other hand, the other way you can handle this is
download the main exe file, close everything window wise and
run that.



On 31/08/2017 6:39 p.m., Akbar S. Currim wrote:
I retried the update with the same result and installation
failed.
The update downloaded fine and then stated that my existing
copy would be updated and asked me to click OK which I did.
After that I keep getting a message saying "please wait-your
existing copy of NVDA is being updated" and this goes on
repeating with simultaneous beeps indefinitely untill finally
it says that the update installation failed. How do I get
over this problem? Should I remove the existing copy of NVDA
and install a fresh copy from scratch?

Alternatively, is it possible to make a portable copy from my
other laptop which has a proper working version and try to
reinstall from that? In that case if it is possible, then I
would be spared from reconfiguring NVDA all over again to
suit my needs.
Thanks,
Akbar


On 8/29/17, Akbar S. Currim <raahzam@gmail.com> wrote:
I got no such notification on either of the laptops. Anyway
I will try your suggestion tomorrow as I am travelling now.
Will get back to you after that with the result.

Thanks,

Akbar

On 8/29/17, Quentin Christensen <quentin@nvaccess.org> wrote:
When you go to install a program, Windows pops up a dialog
advising that you are about to change the system and you
need to accept that before you can install the program.
Sometimes this dialog appears behind other windows. In
that case, you may need to alt+tab to it if it doesn't seem
to appear.

That is usually the reason for this kind of problem.

Regards

Quentin.

On Tue, Aug 29, 2017 at 5:09 PM, Akbar S. Currim
<raahzam@gmail.com>
wrote:

Hi,

I tried to install NVDA17.3 on my HP laptop and although I
could download the new version without any difficulty and
also after clicking to install it when I got the message
to do so the configuring progress went on and on for at
least 20 minutes and after that I got an error message
saying that the installation failed. I tried the same
thing three times with the same result. Could someone
please enlighten me as to what is happening and how I
could remedy the same.

Incidentally I had no problem updating NVDA on my second
laptop which is an Asus. Both laptops are running Win 10
duly updated to the latest version. On the second laptop
the installation took only a few minutes and there was no
problem at all.

I give below the log I received for the installation failure.
Any
help would be greatly appreciated.

Thanks and regards,

Akbar

Log for failure:
INFO - __main__ (10:41:42.874):
Starting NVDA
INFO - core.main (10:41:43.140):
Config dir: C:\Users\Akbar\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (10:41:43.140):
Loading config:
C:\Users\Akbar\AppData\Roaming\nvda\nvda.ini
INFO - core.main (10:41:43.154):
NVDA version 2017.3
INFO - core.main (10:41:43.154):
Using Windows version 10.0.15063 workstation INFO -
core.main (10:41:43.154):
Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17
2016,
20:42:59) [MSC v.1500 32 bit (Intel)] INFO - core.main
(10:41:43.154):
Using comtypes version 0.6.2 INFO -
synthDriverHandler.setSynth (10:41:43.940):
Loaded synthDriver eloquence INFO - core.main
(10:41:43.940):
Using wx version 3.0.2.0 msw (classic) INFO -
brailleInput.initialize (10:41:43.940):
Braille input initialized
INFO - braille.initialize (10:41:43.940):
Using liblouis version 3.2.0 INFO -
braille.BrailleHandler.setDisplayByName (10:41:43.940):
Loaded braille display driver noBraille, current display
has 0 cells.
WARNING - core.main (10:41:43.994):
Java Access Bridge not available INFO -
_UIAHandler.UIAHandler.MTAThreadFunc (10:41:43.994):
UIAutomation: IUIAutomation3 INFO - core.main
(10:41:45.861):
NVDA initialized
ERROR - gui.installerGui.doInstall (11:26:41.197):
Failed to execute installer Traceback (most recent call
last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 182, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by
the user.
ERROR - gui.installerGui.doInstall (11:26:41.198):
Installation failed: [Error 1223] The operation was
canceled by the user.



--
Quentin Christensen
Training and Support Manager

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

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
.


--
search for me on facebook, google+, orkut..
austinpinto.xaviers@gmail.com
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3







--
we have not sent you but as a mercy to the creation.
holy quran, chapter 21, verse 107.
in the very authentic narration is:
imam hosein is the beacon of light and the ark of salvation.
best website for studying islamic book in different languages
al-islam.org













********************************************************************************************************************

This message may contain confidential information. If you are not the intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take any action in relation to its contents. To do so is strictly prohibited and may be unlawful. Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.

For more information and to find out how you can switch, https://portal.nhs.net/help/joiningnhsmail


thunderbird add on

Don H
 

A short while ago someone on the list recommended a Thunderbird add on that allowed single letter navigation of the folder tree in Thunderbird.  Can someone give the name of that add on again.

Thanks


Re: jdf2dic

Ricardo Leonarczyk
 

Hi,

Well, I think it's possible to convert from .jdf to .dic to some
extent. Obviously, some things like sounds and other stuff not
currently present in NVDA will just have to be ignored.
I wasn't able to find any documentation on the jdf formatte, so I
assume one would need to do some reverse engineering e.g., try
creating various kinds of dictionary entries and see what happens to
the file.
Now, maybe this file you want to convert is a simple case and you can
just use regular expressions on the notepad++ or similar to make the
conversion. A tool to do this would be nice I think, but I'm not sure
if creating such a tool would be legal.
Is this jdf file available for download?


2017-09-05 14:44 GMT-03:00, Engin Albayrak <mealbayrak@gmail.com>:

Hello. In Turkey,We are using a jaws dictionary file for QuentinC's playroom
application to translate to Turkish. Because, the app and server doesn't
support Turkish language.
This jdf file is about 70 pages, and it contains about 2000 entry.
I want to edit it as a dic file for nvda.
Does anybody have any idea?
Thanks.





Re: NVDA constantly repeating icons on the desktop

Chris
 

Probably because the screen is being refreshed that can cause it to do this

Hit F5  On the desktop to simulate this

 

 


Re: Github

Quentin Christensen
 

Odd, it seems to be working for me.  Can anyone else reproduce this problem?


Press TAB four times to get to the Browse button and then press spacebar or enter to activate it.  It should bring up a standard Windows file open dialog.

Otherwise, the only thing I can think of, is whether you had explorer crashed or busy in the background or something?

Regards

Quentin.

On Wed, Sep 6, 2017 at 6:17 PM, Brian's Mail list account via Groups.Io <bglists@...> wrote:
It did not work in firefox either, I think short fragments of the log in the body are OK its other files that you really need to attach in case they get corrupted.
It seems to me that the browse, um does not browse ..!
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sarah k Alawami" <marrie12@...>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github


How odd. What shoudl happen si syou hit brows and the file dialogue shoudl appear, it does under safari. Try chrome maybe and see if that works and or firefox or edge?

Good luck.
On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra <cearbhall.omeadhra@...> wrote:

Quentin,

Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather than simply pasting in the contents of the log file, for instance . The problem is that I cannot get any option to attach a file when I clicked on the “browse” button. It would be a great help if you could explain how to attach a file using NVDA.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@... <mailto:cearbhall.omeadhra@blbc.ie>




From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>] On Behalf Of Quentin Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or generally report something that isn't working / could work better / should be implemented etc, what you want to do is create a new issue.  The link to the issues section is https://github.com/nvaccess/nvda/issues <https://github.com/nvaccess/nvda/issues>

Unless you are writing code yourself, you can mostly ignore the other sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to search for the issue you want to report.  (the first one searches code and other things, you want to search issues).  So, if someone reported a problem with footnotes in Word 2016 for instance, I'd search for "word 2016 footnotes" or similar in that second edit box.  There are two types of issues, open and closed. Open issues are either new issues that haven't been triaged yet (that is, no one has looked at them to see how serious they are, whether the issue has already been reported etc), or issues which are being worked on, or waiting to be worked on.  Closed issues are issues which have either been fixed, or which are duplicates of other issues, or sometimes things which can't or won't be fixed.  If the problem with footnotes is that you want them to appear at the top of the page for instance, then that isn't something related to NVDA.  That's a feature request for Word itself and you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump straight there with https://github.com/nvaccess/nvda/issues/new <https://github.com/nvaccess/nvda/issues/new>

When you create a new issue, there is a block of text in the "comment" prompting you for the kinds of information that are useful in diagnosing the issue.  Please try and include: steps to reproduce the issue, attach any files which might help (eg if Word crashes every time you try and check formatting in this particular file, if you can share it, that would help), what should happen and what actually happens, and your system configuration (Windows version, application version, NVDA version and whether installed or portable), and anything you've done to try and resolve or get more information (eg tried different version of NVDA or other program).  Don't stress if you don't have every piece of that information or if you aren't sure if the issue has been filed before. When someone goes to triage the issue, they will ask for more information if needed.  If the issue has been filed previously, they will link to it (and likely close the duplicate issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@... <mailto:linomorales001@...om>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing as heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site.  I haven't signed up yet but it looks easy to do so and to create a pull request, which I assume is what is generally referred to on this list as a ticket.  But many people may find the page confusing. Is there a way that some sort of short help information can be inserted after the navigation links on the page, instructing people what to do to create what are called tickets, perhaps also how to search for tickets and how to create an account?  If tickets are desired from the widest variety of users, this process should be somehow explained and done so in a place that those wishing to create tickets will be likely to see the explanation.

Gene




--
Quentin Christensen
Training and Support Manager

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

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









--
Quentin Christensen
Training and Support Manager

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

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


Re: New NVDA sounds

Quentin Christensen
 

Mostly just to back up what others have said and give a bit more background.  Initially, the idea was simply to "refresh" the sounds, much like we have also done with the logo in 2017.3.  It wasn't that nobody liked them, but it was really split - there were people who preferred the old sounds, some who liked the new sounds, and some who wanted to change the sounds, but didn't like the new ones either.  We hadn't considered that until the feedback started coming in from the snapshot users.  We realised then that what we needed to implement, more than just a new set of sounds on its own, was a way for people to be able to change their own sounds.  One idea for this is along the lines of the way you can install add-ons.  Ideally, unlike add-ons, we want something that will be a bit easier for users to package without needing programming skills.

Because of the divided feedback, we decided the best option (since it hadn't yet rolled out to the majority of users), was to pull the new sounds while we work on this new sound "theme" feature.

So, that's where it's at currently, and I believe someone else has provided instructions in this thread for your question.  Note that if you do that, keep a backup of the sounds as they may get overridden when you update NVDA, and they'll be easier to swap back if you've got the files handy.

Regards

Quentin.

On Wed, Sep 6, 2017 at 9:37 AM, Christopher-Mark Gilland <clgilland07@...> wrote:
Guys,
 
I was running, a while back a snapshot of NVDA 2017.3, and noticed that the NVDA sounds for things like startup, quitting, etc. were different than what they have been for the longest time.
 
Now, with the official release of 2017.3, I'm not seeing this.
 
Can someone advise me on how to go about getting those other sounds? I liked them much better.
 
Chris.
---
Christopher Gilland
Co-founder of Genuine Safe Haven Ministries
 




--
Quentin Christensen
Training and Support Manager

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

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


Re: Github

Bhavya shah
 

Hi all,
I see that a lot of NVDA users seem interested in helping out with
testing NVDA, sharing feedback, reporting bugs, etc. As an active
triager on the NVDA Github issue tracker (along with some other NVDA
community members), we try to make sure that all tickets are
systematic and well-defined, so that developers have sufficient
diagnostic information or compelling use cases ensuring that the
accepted suggestions are easy better understood and consequently
simpler to implement. Therefore, I fortunately have notable experience
in the past month or so with the issue filing side of Github,
knowledge that I would definitely be interested in passing on. I am
considering writing a comprehensive multi-part guide about filing
issues about NVDA on the Github tracker and other less emphasized and
unmentioned essentials you may want to keep in mind while doing the
same in the form of a blog post on my personal blog (Hiking Across
Horizons - bhavyashah125.wordpress.com). Unfortunately, I will not be
able to get to this blog post idea till the 27th September at least
due to upcoming academic commitments, so please expect to hear from me
in this regard post that date, hopefully. Just thought I'd give a
heads-up.
Thanks.

On 9/6/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
It did not work in firefox either, I think short fragments of the log in the

body are OK its other files that you really need to attach in case they get

corrupted.
It seems to me that the browse, um does not browse ..!
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Sarah k Alawami" <marrie12@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Wednesday, September 06, 2017 5:31 AM
Subject: Re: [nvda] Github


How odd. What shoudl happen si syou hit brows and the file dialogue shoudl
appear, it does under safari. Try chrome maybe and see if that works and or

firefox or edge?

Good luck.
On Sep 5, 2017, at 10:21 AM, Cearbhall O'Meadhra
<cearbhall.omeadhra@blbc.ie> wrote:

Quentin,

Thanks for this excellent explanation!

I am being asked to attach the actual text file to a new issue rather than

simply pasting in the contents of the log file, for instance . The problem

is that I cannot get any option to attach a file when I clicked on the
“browse” button. It would be a great help if you could explain how to
attach a file using NVDA.

All the best,

Cearbhall

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@blbc.ie
<mailto:cearbhall.omeadhra@blbc.ie>




From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
[mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>] On Behalf Of
Quentin Christensen
Sent: Monday, September 4, 2017 4:59 AM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Github

As mentioned, if you want to create a ticket, submit an issue or generally

report something that isn't working / could work better / should be
implemented etc, what you want to do is create a new issue. The link to
the issues section is https://github.com/nvaccess/nvda/issues
<https://github.com/nvaccess/nvda/issues>

Unless you are writing code yourself, you can mostly ignore the other
sections (code, pull requests, projects, etc).

Ideally, it's worth jumping to the SECOND edit box on that page to search

for the issue you want to report. (the first one searches code and other

things, you want to search issues). So, if someone reported a problem
with footnotes in Word 2016 for instance, I'd search for "word 2016
footnotes" or similar in that second edit box. There are two types of
issues, open and closed. Open issues are either new issues that haven't
been triaged yet (that is, no one has looked at them to see how serious
they are, whether the issue has already been reported etc), or issues
which are being worked on, or waiting to be worked on. Closed issues are

issues which have either been fixed, or which are duplicates of other
issues, or sometimes things which can't or won't be fixed. If the problem

with footnotes is that you want them to appear at the top of the page for

instance, then that isn't something related to NVDA. That's a feature
request for Word itself and you'd need to submit that to Microsoft.

To create a new issue, there is a "new issue" button, you can jump
straight there with https://github.com/nvaccess/nvda/issues/new
<https://github.com/nvaccess/nvda/issues/new>

When you create a new issue, there is a block of text in the "comment"
prompting you for the kinds of information that are useful in diagnosing
the issue. Please try and include: steps to reproduce the issue, attach
any files which might help (eg if Word crashes every time you try and
check formatting in this particular file, if you can share it, that would

help), what should happen and what actually happens, and your system
configuration (Windows version, application version, NVDA version and
whether installed or portable), and anything you've done to try and
resolve or get more information (eg tried different version of NVDA or
other program). Don't stress if you don't have every piece of that
information or if you aren't sure if the issue has been filed before.
When someone goes to triage the issue, they will ask for more information

if needed. If the issue has been filed previously, they will link to it
(and likely close the duplicate issue you created).

If you do have any more questions, please feel free to ask.

Kind regards

Quentin.



On Mon, Sep 4, 2017 at 2:40 AM, Lino Morales <linomorales001@gmail.com
<mailto:linomorales001@gmail.com>> wrote:
Good point sir. Ive seen Get Hub's pages in the past and its confusing as

heck.


On 9/3/2017 7:34 AM, Gene wrote:
I just looked at the Github NVDA part of the site. I haven't signed up
yet but it looks easy to do so and to create a pull request, which I
assume is what is generally referred to on this list as a ticket. But
many people may find the page confusing. Is there a way that some sort of

short help information can be inserted after the navigation links on the
page, instructing people what to do to create what are called tickets,
perhaps also how to search for tickets and how to create an account? If
tickets are desired from the widest variety of users, this process should

be somehow explained and done so in a place that those wishing to create
tickets will be likely to see the explanation.

Gene




--
Quentin Christensen
Training and Support Manager

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

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





--
Best Regards
Bhavya Shah

Blogger at Hiking Across Horizons: https://bhavyashah125.wordpress.com/

Contacting Me
E-mail Address: bhavya.shah125@gmail.com
Follow me on Twitter @BhavyaShah125 or www.twitter.com/BhavyaShah125
Mobile Number: +91 7506221750


Re: nvdaremote

Jonathan Milam
 

It looks like it.  Does anyone have an update on this one?  I rely on NVDARemote for my job.

 

Thanks,

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of mattias
Sent: Wednesday, September 06, 2017 5:21 AM
To: nvda@nvda.groups.io
Subject: [nvda] nvdaremote

 

Are the nvdaremote server down?

 

Skickades från E-post för Windows 10

 


Re: one core voice install

Quentin Christensen
 

Go into region and language, install a language, then choose English, and from there choose whichever variant you want (Australian, Canadian, Irish etc).

Then make sure you go into that language and install the speech pack.

On Wed, Sep 6, 2017 at 8:57 AM, mr. Chikodinaka Nickarandidum Oguledo <ochikodinaka@...> wrote:
can I hear a demo of voices NVDA?

On 9/5/17, Darren Tomblin <dtomblin@...> wrote:
> hi, on my win10 system i'm trying to install additional one core voice
> and I can't figure out how to do it. I go into region and languages and
> I don't see where to add the other english voices. can someone help me
> with this. thanks
>
> --
> 73,
> Darren Tomblin(KC9JJJ)
>
>
>
>
>


--
for if you persavear. you will conker never fear. try try try again






--
Quentin Christensen
Training and Support Manager

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

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


nvdaremote

mattias
 

Are the nvdaremote server down?

 

Skickades från E-post för Windows 10