Date   

Re: Joseph Lee's add-ons: mandatory update for add-ons to be released in the next few hours #addonrelease

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

Well that means you do not have the same add ons as I do I would imagine.
I wonder what the situation is for a machine running the previous stable version as I see the last update of add on updater has removed the add on update entry from the menu, meaning that any updates to older nvda versions are now manual again.
Brian

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

----- Original Message -----
From: "Brian Vogel" <britechguy@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Thursday, January 31, 2019 5:07 PM
Subject: Re: [nvda] Joseph Lee's add-ons: mandatory update for add-ons to be released in the next few hours #AddonRelease


I got nothing last night before retiring. As of a few moments ago I got the group of three, but even after exiting NVDA and restarting there's been no fourth as a single item.

--

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

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

~ Saul Bellow, To Jerusalem and Back


Re: bug with nvda selection

 

Well to be honest, until there is a good design, then it should be able to work with jaws.

Freedomscientiffic is one of the oldest companies, and the way vispero has pushed itself its ensured that it is.

Reguardless of any of your feelings on jaws, yes I have some vary strong feelings round the licencing of jaws, the cost of jaws and I know well enough that some of you have issues with support people there to.

Never the less, like google and others, if it will work on jaws, then there is a really  good chance excluding the scripts of course thats its going to work on nvda or anything else for that matter.

As long as it complies with all the access guidelines as well as the jaws guidelines, excluding jaws scripts of course, then its probably garanteed to run without issue.

Now you can write the program properly, or script it for the readers you want.

Then again, you can probably use tolque or other libraries I think there are a couple that have the controler libraries of the dolphin, windoweyes, jaws and nvda loaded and if it runs to standard its going to work.

Failing that, if you really don't want to bother with that, making it as web friendly as you can will work, and if you really couldn't care less, you may get away with having it run from a brouser  though you will have some other restrictions.

The issue would be if you wanted to use custom images, a custom nonstandard interface or non standard controls.

Thats a lot less commen than it used to be a couple years ago with a lot of stuff being web centric.

Now while nvda can run standard programs and even a few non standard ones with ocr it seems to lend itself to a web style interface.

So programs like thunderbird which are basically glorified web apps will just work for the most part.

On 1/02/2019 9:04 PM, Felix G. wrote:
Hi!
The problem with the argument from good design is that there exists no
public definition of what would constitute good design where a screen
reader is concerned. Until we have some science, in terms of studies,
to back up what good screen reader user experience actually means,
it's all a matter of preference. The recent survey may provide some
valid data points but by its nature it primarily selects
English-speaking members of a certain small set of email lists. I
still think the survey was a good idea. I'm merely objectively
pointing out its restrictions.
Also, I don't think that not giving enough credit to blind people is a
relevant factor. Such appeals to guilt only cloud the view and make
people feel bad.
My two cents,
Felix

Am Fr., 1. Feb. 2019 um 03:42 Uhr schrieb Gene <gsasner@gmail.com>:
That goes against good design and against the philosophy behind the design of NVDA. Selecting text should follow the same principle as when you select by character with the application cursor in Windows. On what basis was it decided that NVDA should have its own selection rules that are completely nonstandard? Why not give blind people enough credit to believe that they can select correctly using screen review commands?

Gene
----- Original Message -----
From: Quentin Christensen
Sent: Thursday, January 31, 2019 7:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] bug with nvda selection

Because you may not be able to move past the last character with the review cursor, as you usually can in say Word, NVDA selects the character beyond the last one selected to ensure you get everything. Because of that, it works slightly differently to regular copy, but that's the reasoning. But yes, you do need to press NVDA+F9, then select all (but the last character) of the text you want to copy first. Then press NVDA+F10 twice quickly to select and copy.

Kind Regards

Quentin.

On Fri, Feb 1, 2019 at 4:21 AM Gene <gsasner@gmail.com> wrote:
This isn't a bug. You must move to the last letter of the last word before copying to the clipboard. If you are moving by word, you are moving to the beginning of the word and must move by character to the last character.

Gene
----- Original Message -----
From: enes sarıbaş
Sent: Thursday, January 31, 2019 11:15 AM
To: nvda@nvda.groups.io
Subject: [nvda] bug with nvda selection

hi,

When I use NVDA+f9 to select, and move to a word, and press nvda f10 to
copy, NVDA only copies the first letter of the last word selected. Does
anyone else experience this or know of a solution?


--
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: bug with nvda selection

Felix G.
 

Hi!
The problem with the argument from good design is that there exists no
public definition of what would constitute good design where a screen
reader is concerned. Until we have some science, in terms of studies,
to back up what good screen reader user experience actually means,
it's all a matter of preference. The recent survey may provide some
valid data points but by its nature it primarily selects
English-speaking members of a certain small set of email lists. I
still think the survey was a good idea. I'm merely objectively
pointing out its restrictions.
Also, I don't think that not giving enough credit to blind people is a
relevant factor. Such appeals to guilt only cloud the view and make
people feel bad.
My two cents,
Felix

Am Fr., 1. Feb. 2019 um 03:42 Uhr schrieb Gene <gsasner@gmail.com>:


That goes against good design and against the philosophy behind the design of NVDA. Selecting text should follow the same principle as when you select by character with the application cursor in Windows. On what basis was it decided that NVDA should have its own selection rules that are completely nonstandard? Why not give blind people enough credit to believe that they can select correctly using screen review commands?

Gene
----- Original Message -----
From: Quentin Christensen
Sent: Thursday, January 31, 2019 7:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] bug with nvda selection

Because you may not be able to move past the last character with the review cursor, as you usually can in say Word, NVDA selects the character beyond the last one selected to ensure you get everything. Because of that, it works slightly differently to regular copy, but that's the reasoning. But yes, you do need to press NVDA+F9, then select all (but the last character) of the text you want to copy first. Then press NVDA+F10 twice quickly to select and copy.

Kind Regards

Quentin.

On Fri, Feb 1, 2019 at 4:21 AM Gene <gsasner@gmail.com> wrote:

This isn't a bug. You must move to the last letter of the last word before copying to the clipboard. If you are moving by word, you are moving to the beginning of the word and must move by character to the last character.

Gene
----- Original Message -----
From: enes sarıbaş
Sent: Thursday, January 31, 2019 11:15 AM
To: nvda@nvda.groups.io
Subject: [nvda] bug with nvda selection

hi,

When I use NVDA+f9 to select, and move to a word, and press nvda f10 to
copy, NVDA only copies the first letter of the last word selected. Does
anyone else experience this or know of a solution?



--
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: bug with nvda selection

Raha Tehrani
 

Hi.
you are right. the same problem exists. it's taken place several times
in my case, I've selected a few lines and I moved to the last letter
of the last word. but NVDA appeared just to select one letter. it was
fixed after I unloaded and reloaded NVDA. I don't have any idea why it
happened but it exists.

On 2/1/19, Gene <gsasner@gmail.com> wrote:
That goes against good design and against the philosophy behind the design
of NVDA. Selecting text should follow the same principle as when you select
by character with the application cursor in Windows. On what basis was it
decided that NVDA should have its own selection rules that are completely
nonstandard? Why not give blind people enough credit to believe that they
can select correctly using screen review commands?

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

From: Quentin Christensen
Sent: Thursday, January 31, 2019 7:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] bug with nvda selection


Because you may not be able to move past the last character with the review
cursor, as you usually can in say Word, NVDA selects the character beyond
the last one selected to ensure you get everything. Because of that, it
works slightly differently to regular copy, but that's the reasoning. But
yes, you do need to press NVDA+F9, then select all (but the last character)
of the text you want to copy first. Then press NVDA+F10 twice quickly to
select and copy.


Kind Regards


Quentin.


On Fri, Feb 1, 2019 at 4:21 AM Gene <gsasner@gmail.com> wrote:

This isn't a bug. You must move to the last letter of the last word
before copying to the clipboard. If you are moving by word, you are moving
to the beginning of the word and must move by character to the last
character.

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

From: enes sarıbaş
Sent: Thursday, January 31, 2019 11:15 AM
To: nvda@nvda.groups.io
Subject: [nvda] bug with nvda selection


hi,

When I use NVDA+f9 to select, and move to a word, and press nvda f10 to
copy, NVDA only copies the first letter of the last word selected. Does
anyone else experience this or know of a solution?










--

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: bug with nvda selection

Gene
 

That goes against good design and against the philosophy behind the design of NVDA.  Selecting text should follow the same principle as when you select by character with the application cursor in Windows.  On what basis was it decided that NVDA should have its own selection rules that are completely nonstandard?  Why not give blind people enough credit to believe that they can select correctly using screen review commands?
 
Gene

----- Original Message -----
Sent: Thursday, January 31, 2019 7:45 PM
Subject: Re: [nvda] bug with nvda selection

Because you may not be able to move past the last character with the review cursor, as you usually can in say Word, NVDA selects the character beyond the last one selected to ensure you get everything.  Because of that, it works slightly differently to regular copy, but that's the reasoning.  But yes, you do need to press NVDA+F9, then select all (but the last character) of the text you want to copy first.  Then press NVDA+F10 twice quickly to select and copy.

Kind Regards

Quentin.

On Fri, Feb 1, 2019 at 4:21 AM Gene <gsasner@...> wrote:
This isn't a bug.  You must move to the last letter of the last word before copying to the clipboard.  If you are moving by word, you are moving to the beginning of the word and must move by character to the last character.
 
Gene
----- Original Message -----
Sent: Thursday, January 31, 2019 11:15 AM
Subject: [nvda] bug with nvda selection

hi,

When I use NVDA+f9 to select, and move to a word, and press nvda f10 to
copy, NVDA only copies the first letter of the last word selected. Does
anyone else experience this or know of a solution?





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


never mind, about the level thing

Annette Moore
 

I answered my own question. I had to go uncheck something in the view menu, in "sort by".

Annette


getting rid of the levels

Annette Moore
 

Hi, guys,

Yep, I know it's a funny-sounding subject, but there it is. this question is in regard to thunderbird. something must've gotten messed up because I've had to redo some of my column work, and now when I go through messages, it says, level 1, level 2, level 3, etc. How do I get it to stop that? It wasn't doing that before. It's driving me nuts! LOL! take away the levels! Hahahaha!

Annette


Re: bug with nvda selection

Quentin Christensen
 

Because you may not be able to move past the last character with the review cursor, as you usually can in say Word, NVDA selects the character beyond the last one selected to ensure you get everything.  Because of that, it works slightly differently to regular copy, but that's the reasoning.  But yes, you do need to press NVDA+F9, then select all (but the last character) of the text you want to copy first.  Then press NVDA+F10 twice quickly to select and copy.

Kind Regards

Quentin.

On Fri, Feb 1, 2019 at 4:21 AM Gene <gsasner@...> wrote:
This isn't a bug.  You must move to the last letter of the last word before copying to the clipboard.  If you are moving by word, you are moving to the beginning of the word and must move by character to the last character.
 
Gene
----- Original Message -----
Sent: Thursday, January 31, 2019 11:15 AM
Subject: [nvda] bug with nvda selection

hi,

When I use NVDA+f9 to select, and move to a word, and press nvda f10 to
copy, NVDA only copies the first letter of the last word selected. Does
anyone else experience this or know of a solution?





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


found extension to play sounds in firefox how to contact developer

Dennis L <dennisl1982@...>
 

Hi, I found an extension to add sounds to Firefox how do I contact the developer?  Hear is the link.

https://addons.mozilla.org/en-US/firefox/addon/extra-sounds/?src=search

 


Re: Intro.

Quentin Christensen
 

Welcome Pramit!

Do feel free to ask any questions (or share any tips or ideas) you come up with.

Kind regards
Quentin.

On Thu, Jan 31, 2019 at 10:36 PM Pramit <PRAMIT.VISION@...> wrote:

Hi everyone,


Although it's been a while since I've joined this group, I guess I couldn't properly introduce myself. I am Pramit. I am visually impaired and cannot read at all.


As my vision kept dropping, technology (mobile & PC) has had a huge impact as it has enabled me to still continue to work independently, be productive at work and be socially connected.


I am extremely passionate about building better tech solutions for all of us. With divine grace, I have managed to put together a tech startup with an equally motivated partner.


Amongst my interest, I am a voracious reader (hearer of audiobooks), I love meditating and I am also an experimental cook, results of one can lead to wow to only I will have to eat situation. I was lucky enough to reverse my diabetes through significant lifestyle changes about 10 years back. Sharing my learning and motivating others online is another passion/interest area. I do this strictly on a non-commercial basis. Link below:

https://www.youtube.com/watch?v=2knVCQE9_70


Thanks 

Pramit




--
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: NVDA and Excel

Quentin Christensen
 

Ok that issue is one I know how to fix.  We're working to get a proper fix implemented, but in the meantime, what you can do is disable "Allow editing directly in cells":

1. Open Excel
2. Press ALT+F, then T to open the options
3. Press CONTROL+TAB several (Seven on mine) times to get to "Advanced" options.
4. Press ALT+E to toggle "Allow editing directly in cells".  You want to ensure this is unchecked.
5. Press ENTER to accept the changes.

You should now be able to edit the contents of cells and have NVDA report correctly.  If you have sight, one visual difference is that when editing cells, the focus is on the formula bar above the worksheet, whereas with that setting checked, the focus stays in the cell itself - but the end result is the same.

Kind regards

Quentin.

On Thu, Jan 31, 2019 at 7:45 PM Supanut Leepaisomboon <supanut2000@...> wrote:
Hi,
I think I'm having similar, if not exactly the same, issue.
Basically, in Excel, when typing in a cell NVDA won't announce the character when I pressed the backspace key, or when I used the left/right arrow keys to move through the content of the cell. In addition, when I start typing into a cell, NVDA would say 'unknown'.



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


Add-on Updater: 19.02.1A emergency patch. manual update required

 

Hi all,

 

Shortly after release of Add-on Updater 19.02.1, a user told me that it fails to work on NVDA 2018.4.1. The problem was traced to instance checking for add-on manifest keys and a fix was pushed to add-ons server. Because this problem affects NVDA 2018.4.1, I advise applying the upcoming update (19.02.1A) manually (please wait half an our before going to addons.nvda-project.org).

 

Thanks, and sorry for the inconvenience.

Cheers,

Joseph


Re: Before I fill out the survey

Gene
 

What are you describing?  You talk about focus moving when you switch to another document but what is the problem you are discussing?  Focus moves to that document.  As far as I know, you keep your place when you return.  and focus in Windows , the operating system, does also.
 
Gene

----- Original Message -----
Sent: Thursday, January 31, 2019 12:22 PM
Subject: Re: [nvda] Before I fill out the survey

Good Morning:  I have to agree with you on the focus moving in your
comment.  However, I would think this thought needs to go farther.  This
needs to be carried to as far as the the focus moving from where you are
reading to another place in any document or web page.  This should even
true for in windows settings.

Dave


On 1/23/2019 3:01 AM, Brian's Mail list account via Groups.Io wrote:
> That is very true and of course, one also needs to set reasonable
> defaults as its compounded if an issue is actually du to a setting
> that people would not expect to affect a certain thing, but does. The
> one I'm thinking of is the onees regarding the switching between focus
> and browse mode on edit areas. Sometimes it better one way sometimes
> another and its hard to see how you can tell in advance which way
> around a given site might work best with.
> Brian
>
> bglists@...
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Quentin Christensen"
> <quentin@...>
> To: <nvda@nvda.groups.io>
> Sent: Wednesday, January 23, 2019 12:53 AM
> Subject: Re: [nvda] Before I fill out the survey
>
>
>> I was also going to say that there is also value in knowing what
>> users are
>> having trouble with - if it's a matter of something which has a
>> keystroke /
>> setting / existing way to fix it, that's great and makes it easy to help
>> the individual, but us learning that people are getting stuck with
>> something is useful as well.  There's no point in us thinking we've
>> solved
>> a problem by adding a keystroke or setting if no-one is aware it is
>> exists
>> :)
>>
>> On Wed, Jan 23, 2019 at 9:00 AM Brian Vogel <britechguy@...>
>> wrote:
>>
>>> I would also argue that regardless of whether there is a "way
>>> around" the
>>> issues you're encountering, there is great value in a development
>>> team for
>>> any product to know about issues that require "ways around" that
>>> irritate
>>> users to no end.
>>>
>>> Sometimes highly skilled users of certain software, not just NVDA, lose
>>> all perspective of what the experience is like for the
>>> unsophisticated user
>>> (and that term is not an insult, personal or otherwise, we were all
>>> unsophisticated users of everything we've ever touched at one point in
>>> time).   Having that input can result in improvements that would not
>>> otherwise have been contemplated because there was no awareness of
>>> need or
>>> desire.
>>>
>>> --
>>>
>>> Brian *-* Windows 10 Home, 64-Bit, Version 1809, Build 17763
>>>
>>> *A great deal of intelligence can be invested in ignorance when the
>>> need
>>> for illusion is deep.*
>>>
>>>           ~ Saul Bellow, *To Jerusalem and Back*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>> --
>> 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: Before I fill out the survey

Dave Grossoehme
 

Good Morning:  I have to agree with you on the focus moving in your comment.  However, I would think this thought needs to go farther.  This needs to be carried to as far as the the focus moving from where you are reading to another place in any document or web page.  This should even true for in windows settings.

Dave

On 1/23/2019 3:01 AM, Brian's Mail list account via Groups.Io wrote:
That is very true and of course, one also needs to set reasonable defaults as its compounded if an issue is actually du to a setting that people would not expect to affect a certain thing, but does. The one I'm thinking of is the onees regarding the switching between focus and browse mode on edit areas. Sometimes it better one way sometimes another and its hard to see how you can tell in advance which way around a given site might work best with.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail 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, January 23, 2019 12:53 AM
Subject: Re: [nvda] Before I fill out the survey


I was also going to say that there is also value in knowing what users are
having trouble with - if it's a matter of something which has a keystroke /
setting / existing way to fix it, that's great and makes it easy to help
the individual, but us learning that people are getting stuck with
something is useful as well.  There's no point in us thinking we've solved
a problem by adding a keystroke or setting if no-one is aware it is exists
:)

On Wed, Jan 23, 2019 at 9:00 AM Brian Vogel <britechguy@gmail.com> wrote:

I would also argue that regardless of whether there is a "way around" the
issues you're encountering, there is great value in a development team for
any product to know about issues that require "ways around" that irritate
users to no end.

Sometimes highly skilled users of certain software, not just NVDA, lose
all perspective of what the experience is like for the unsophisticated user
(and that term is not an insult, personal or otherwise, we were all
unsophisticated users of everything we've ever touched at one point in
time).   Having that input can result in improvements that would not
otherwise have been contemplated because there was no awareness of need or
desire.

--

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

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

          ~ Saul Bellow, *To Jerusalem and Back*






--
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: Add-on Updater: version 19.02.1 emergency manual patch #addonrelease

 

Hi,

Try checking for add-on updates manually.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Darren Harris via Groups.Io
Sent: Thursday, January 31, 2019 10:04 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Add-on Updater: version 19.02.1 emergency manual patch #AddonRelease

 

According to my app I’m running 19.02 can’t see a 19.02.1 I’m using the latest stable NVDA v2018.4.1. I just tried the check for addon updates and it didn’t say anything.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: 31 January 2019 17:58
To: 'NVDA screen reader development' <nvda-devel@...>
Subject: [nvda] Add-on Updater: version 19.02.1 emergency manual patch #AddonRelease

 

Hi everyone,

For users of Add-on Updater: if you are using NVDA alpha build 16682 and later, there exists a bug in Add-on Updater that prevents you from installing future add-on updates. I have pushed an update to this add-on, but the thing is, you must apply the patch manually if you are indeed running alpha snapshots (those running 2018.4.1 are not affected).

 

If you happen to be running alpha build 16682 and later, go to addons.nvda-project.org, select Add-on Updater, and download stable version. If the version you get is 19.02.1, you’re good to go. For those using 2018.4.1 or an earlier alpha snapshot, I highly encourage you to update to Add-on Updater 19.02.1 via Add-on Updater itself.

 

Thanks.

Cheers,

Joseph


Re: Add-on Updater: version 19.02.1 emergency manual patch #addonrelease

Darren Harris
 

According to my app I’m running 19.02 can’t see a 19.02.1 I’m using the latest stable NVDA v2018.4.1. I just tried the check for addon updates and it didn’t say anything.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: 31 January 2019 17:58
To: 'NVDA screen reader development' <nvda-devel@...>
Subject: [nvda] Add-on Updater: version 19.02.1 emergency manual patch #AddonRelease

 

Hi everyone,

For users of Add-on Updater: if you are using NVDA alpha build 16682 and later, there exists a bug in Add-on Updater that prevents you from installing future add-on updates. I have pushed an update to this add-on, but the thing is, you must apply the patch manually if you are indeed running alpha snapshots (those running 2018.4.1 are not affected).

 

If you happen to be running alpha build 16682 and later, go to addons.nvda-project.org, select Add-on Updater, and download stable version. If the version you get is 19.02.1, you’re good to go. For those using 2018.4.1 or an earlier alpha snapshot, I highly encourage you to update to Add-on Updater 19.02.1 via Add-on Updater itself.

 

Thanks.

Cheers,

Joseph


Add-on Updater: version 19.02.1 emergency manual patch #addonrelease

 

Hi everyone,

For users of Add-on Updater: if you are using NVDA alpha build 16682 and later, there exists a bug in Add-on Updater that prevents you from installing future add-on updates. I have pushed an update to this add-on, but the thing is, you must apply the patch manually if you are indeed running alpha snapshots (those running 2018.4.1 are not affected).

 

If you happen to be running alpha build 16682 and later, go to addons.nvda-project.org, select Add-on Updater, and download stable version. If the version you get is 19.02.1, you’re good to go. For those using 2018.4.1 or an earlier alpha snapshot, I highly encourage you to update to Add-on Updater 19.02.1 via Add-on Updater itself.

 

Thanks.

Cheers,

Joseph


Re: bug with nvda selection

Gene
 

This isn't a bug.  You must move to the last letter of the last word before copying to the clipboard.  If you are moving by word, you are moving to the beginning of the word and must move by character to the last character.
 
Gene

----- Original Message -----
Sent: Thursday, January 31, 2019 11:15 AM
Subject: [nvda] bug with nvda selection

hi,

When I use NVDA+f9 to select, and move to a word, and press nvda f10 to
copy, NVDA only copies the first letter of the last word selected. Does
anyone else experience this or know of a solution?




bug with nvda selection

enes sarıbaş
 

hi,

When I use NVDA+f9 to select, and move to a word, and press nvda f10 to copy, NVDA only copies the first letter of the last word selected. Does anyone else experience this or know of a solution?


Re: Joseph Lee's add-ons: mandatory update for add-ons to be released in the next few hours #addonrelease

 

I got nothing last night before retiring.  As of a few moments ago I got the group of three, but even after exiting NVDA and restarting there's been no fourth as a single item.

--

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

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

          ~ Saul Bellow, To Jerusalem and Back