Am 05.02.2019 um 16:36 schrieb mcLeod stinnett <macks75205@...>:


--
from mack I know there is a way to get to it, but I forgot how to do the link. thanks.

Hi,
When we compare the behavior from last year, the new approach partially
reverses the deal we went through in January. That is, any add-on with no
compatibility flags whatsoever will continue to work and seen as compatible,
whereas those that ships with these flags will need to be modified. This is
bound to change, as new NVDA releases may break compatibility (intentionally
or unintentionally due to something else).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail
list account via Groups.Io
Sent: Tuesday, February 5, 2019 1:02 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Add-on Updater 19.02.2 coming soon (another mandatory
update), enforcing three-part NVDA compatibility flags #AddonRelease

Joseph.
In the latest download of stable, there are very few add ons that are
allowed to be enabled. However only one is flagged at the start, indent nav.
All the others seem to have been disabled silently. It is a huge list of
them which I use on a regular basis, and as I said in my last message. I'm
considering disabling updates in the nvda main version and only having the
latest stable as a portable version until or unless more add ons can be made
to work.
Might I suggest that there is some form of test mode in nvda that allows
people to toggle on incompatible add ons to see if they actually work?
I think this would ease things a lot. I do understand that in the end many
will be seen to be incompatible, but I also feel that the lead time is far
too short to get part time writers to fix them before this new version of
nvda comes out.
People are not doing it as a job after all.
Anyone else care to offer some advice?

The crunch surely will come when python 3 is adopted completely. I do not
know when that will be, but until then I see no reason for doing more than
alerting people It would also be nice to see nvda produce a list of the add
ons that look like they are going to be a no go one when the time comes. At
present there seems no way other than to go to the manage add ons page and
manually list the ones turned off.
I think its quite legitimate to stop add ons being installed if they don't
work but not if they already exist as this is going to cause a lot fo aggro.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: "'NVDA screen reader development'" <nvda-devel@...>
Sent: Tuesday, February 05, 2019 5:40 AM
Subject: [nvda] Add-on Updater 19.02.2 coming soon (another mandatory
update), enforcing three-part NVDA compatibility flags #AddonRelease

Dear NVDA community,



Yes, Add-on Updater 19.02.2 is coming soon. But before going into
that, a bit of an explanation regarding what will happen:



A few days ago NV Access people announced a revised approach to how
NVDA will check for add-on compatibility. Previously, add-on authors
were advised to specify minimum and last tested NVDA version in the
form year.major (e.g.
2018.4). Any add-ons that didn't come with these flags, especially
those that lacked last tested flag, were considered incompatible. In
contrast, the new approach will keep backward compatibility by having
a base API version to which all add-ons are considered compatible
with, and add-on authors advised to update minimum version flag when
breaking changes are introduced.



At the same time, the compatibility range manifest style has changed.
Previously ad-on authors were told to specify compatibility version in
the form year.major. Now, authors must include minor release as well,
so it becomes year.major.minor (e.g. 2018.4.0). For the most part,
authors can leave the minor release as 0.



To enforce the new approach, starting from version 19.02.2, Add-on
Updater will advise you to contact add-on authors and request for a
re-release if compatibility flags do not comply with the newly revised
format. For example, if an add-on update specifies 2018.4.0 as minimum
NVDA version, Add-on Updater won't complain; but if minimum NVDA
version is 2018.4 (just year.major), Add-on Updater will warn you of
this fact and refuse to update until a version of the add-on that does
come with revised compatibility flag format is released.



A few things to note:



* To give time for authors and users to communicate with each other
regarding add-on compatibility checks, this new check will be enforced
if and only if you are running any form of NVDA 2019.1 (alpha, beta,
RC, stable).
* This change will become permanent (as far as Add-on Updater is
concerned) around the time NVDA 2019.1 release candidate (RC) is released.
* For authors, you do not have to specify minor release as part of
compatibility range statement (if your add-on requires NVDA 2018.4.0
in the manifest, you can just say that NVDA 2018.4 is required).



In addition to the change outlined above, Add-on Updater 19.02.2 will
enable update checks for one or two add-ons approved for distribution
on community add-ons website.



Thank you.

Cheers,

Joseph

Joseph.
In the latest download of stable, there are very few add ons that are allowed to be enabled. However only one is flagged at the start, indent nav.
All the others seem to have been disabled silently. It is a huge list of them which I use on a regular basis, and as I said in my last message. I'm considering disabling updates in the nvda main version and only having the latest stable as a portable version until or unless more add ons can be made to work.
Might I suggest that there is some form of test mode in nvda that allows people to toggle on incompatible add ons to see if they actually work?
I think this would ease things a lot. I do understand that in the end many will be seen to be incompatible, but I also feel that the lead time is far too short to get part time writers to fix them before this new version of nvda comes out.
People are not doing it as a job after all.
Anyone else care to offer some advice?

The crunch surely will come when python 3 is adopted completely. I do not know when that will be, but until then I see no reason for doing more than alerting people It would also be nice to see nvda produce a list of the add ons that look like they are going to be a no go one when the time comes. At present there seems no way other than to go to the manage add ons page and manually list the ones turned off.
I think its quite legitimate to stop add ons being installed if they don't work but not if they already exist as this is going to cause a lot fo aggro.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: "'NVDA screen reader development'" <nvda-devel@...>
Sent: Tuesday, February 05, 2019 5:40 AM
Subject: [nvda] Add-on Updater 19.02.2 coming soon (another mandatory update), enforcing three-part NVDA compatibility flags #AddonRelease

Dear NVDA community,



Yes, Add-on Updater 19.02.2 is coming soon. But before going into that, a
bit of an explanation regarding what will happen:



A few days ago NV Access people announced a revised approach to how NVDA
will check for add-on compatibility. Previously, add-on authors were advised
to specify minimum and last tested NVDA version in the form year.major (e.g.
2018.4). Any add-ons that didn't come with these flags, especially those
that lacked last tested flag, were considered incompatible. In contrast, the
new approach will keep backward compatibility by having a base API version
to which all add-ons are considered compatible with, and add-on authors
advised to update minimum version flag when breaking changes are introduced.



At the same time, the compatibility range manifest style has changed.
Previously ad-on authors were told to specify compatibility version in the
form year.major. Now, authors must include minor release as well, so it
becomes year.major.minor (e.g. 2018.4.0). For the most part, authors can
leave the minor release as 0.



To enforce the new approach, starting from version 19.02.2, Add-on Updater
will advise you to contact add-on authors and request for a re-release if
compatibility flags do not comply with the newly revised format. For
example, if an add-on update specifies 2018.4.0 as minimum NVDA version,
Add-on Updater won't complain; but if minimum NVDA version is 2018.4 (just
year.major), Add-on Updater will warn you of this fact and refuse to update
until a version of the add-on that does come with revised compatibility flag
format is released.



A few things to note:



* To give time for authors and users to communicate with each other
regarding add-on compatibility checks, this new check will be enforced if
and only if you are running any form of NVDA 2019.1 (alpha, beta, RC,
stable).
* This change will become permanent (as far as Add-on Updater is
concerned) around the time NVDA 2019.1 release candidate (RC) is released.
* For authors, you do not have to specify minor release as part of
compatibility range statement (if your add-on requires NVDA 2018.4.0 in the
manifest, you can just say that NVDA 2018.4 is required).



In addition to the change outlined above, Add-on Updater 19.02.2 will enable
update checks for one or two add-ons approved for distribution on community
add-ons website.



Thank you.

Cheers,

Joseph

Hi guys!
I always had enough vision that I never felt the need of learning Braille. I'm 22 and wish to learn it now. I need to make frequent presentations in my class, and for now, I try and memorize all the stuff I need to present. It's a difficult and time consuming task, I'm thinking maybe learning Braille could help me in this regard. I see myself in professions which might need frequent public speaking.
What do you guys suggest? Is learning Braille a good idea at this point? How long will it take and how efficient can I get? I have read on this forum that it is very difficult and you can't get very good at it, if you start leaning it at an advanced age.
All feedback is welcome.
Regards

Hey guys, Molly here again.

I’m trying to help a friend with object navigation. Can the insert key be used in object navigation, or does it require just the caps lock key? I have an insert key on my laptop, but it is physically impossible to use object navigation with the insert key due to where it is located on my machine.

Any help will be greatly appreciated.

Thanks.

Molly

Hi guys!
I always had enough vision that I never felt the need of learning Braille.
I'm 22 and wish to learn it now. I need to make frequent presentations
in my class, and for now, I try and memorize all the stuff I need to
present. It's a difficult and time consuming task, I'm thinking maybe
learning Braille could help me in this regard. I see myself in
professions which might need frequent public speaking.

What do you guys suggest? Is learning Braille a good idea at this
point? How long will it take and how efficient can I get? I have read
on this forum that it is very difficult and you can't get very good at
it, if you start leaning it at an advanced age.

All feedback is welcome.

Regards

Hello especially to NVDA developers




I have encountered the very strange behaviour I will describe below and
wonder if there is an explanation or fix for it. This is what happens:




I have noticed this only in Edge. When my laptop runs on its battery and I
do a read to end in Edge, NVDA will read for a few minutes, maybe two or
three minutes, then stops reading. When I move my arrow keys, I notice
that the cursor position is far behind the point where NVDA stopped
reading. When my laptop runs off the mains, this does not happen at all.
NVDA reads continuously for however long I want it to read and the cursor
keeps up with the reading position. I hope this makes sense, because it is
quite bizarre to me.




Kind regards

Christo

I thought you could run a reg file as admin in Windows. I don't see that option in Windows 10. I'll try the built-in admin account later unless other answers say something else.

Travis

Can you run that as admin, or using the hidden admin account?

Take care and happy Monday.

On 4 Feb 2019, at 10:17, Kwork wrote:

I got the following error when executing this command, and of course I don't know which entries failed:

"Cannot import C:\media\reg tweaks\Sound_in_Safe_Mode\Sound_in_Safe_Mode_RegFile.reg: Not all data was successfully written to the registry.  Some keys are open by the system or other processes, or you have insufficient privileges to perform this operation."

On 2/4/2019 10:54 AM, Brian Vogel wrote:

OK, here's the latest, and it should work.

Download the ZIP file on my Google Drive:  Getting Sound in Safe Mode Under Windows 10

The ZIP contains 4 files:

1. Step by step instructions in MS-Word format.
2. Step by step instructions in plain text format.
3. A copy of the registry edit file in plain text format for those who want to examine its contents before running it.
4. The .reg file that can simply be activated once selected to get those registry entries into the system registry.

You only have to run the .reg file once.  Those entries remain in the system registry once they're placed there, so in the future when you boot into Safe Mode, however you do that, you should have sound.

I would appreciate reports back on how this works out as I do not have time to test myself but trust the folks who've examined the .reg script - they know what they're doing.
--

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

 

 

Hello especially to NVDA developers

I have encountered the very strange behaviour I will describe below and wonder if there is an explanation or fix for it. This is what happens:

I have noticed this only in Edge. When my laptop runs on its battery and I do a read to end in Edge, NVDA will read for a few minutes, maybe two or three minutes, then stops reading. When I move my arrow keys, I notice that the cursor position is far behind the point where NVDA stopped reading. When my laptop runs off the mains, this does not happen at all. NVDA reads continuously for however long I want it to read and the cursor keeps up with the reading position. I hope this makes sense, because it is quite bizarre to me.

Kind regards

Christo

Hi guys!
I always had enough vision that I never felt the need of learning Braille.
I'm 22 and wish to learn it now. I need to make frequent presentations in my
class, and for now, I try and memorize all the stuff I need to present. It's
a difficult and time consuming task, I'm thinking maybe learning Braille
could help me in this regard. I see myself in professions which might need
frequent public speaking.

What do you guys suggest? Is learning Braille a good idea at this point? How
long will it take and how efficient can I get? I have read on this forum
that it is very difficult and you can't get very good at it, if you start
leaning it at an advanced age.

All feedback is welcome.

Regards