Date   

Re: not constantly maintained addon and compatibility issue

 

Hi all,

This reminds me of a message posted throughout the NVDA Community a few months ago:

While you can tell NVDA that an add-on is compatible by editing its manifest, not all add-ons will work after you do this. For example, if you think an add-on should be compatible yet is written in Python 2, it will not work because Python itself cannot run add-on modules. Most importantly, even if an add-on is written in Python 3, if it uses removed NVDA features, it will not run properly.

The amount of effort required to get an add-on supported and running well depends on how the add-on source code is structured and features in use. For example, I spent the last 24 hours just updating Clock add-on to use newer NVDA technologies and to clean up the code (time spent includes testing changes), and I plan to optimize the add-on further for speed (this takes more time to do so because it involves techniques not many add-on developers use; one such technique is Python bytecode disassembly).

At this time, I would like to suggest that you tell us names of add-ons that are not working with NVDA 2021.1, and the community will find out if updates are available or someone can maintain them. Also, if you haven't, I advise installing Add-on Updater so you can receive latest add-on updates as they become available.

Cheers,

Joseph


Re: NVDA development course

 

Hi,

Ah, the devlearning subgroup? It was meant to teach folks aobut NVDA code contributions, but it is inactive now. Due to other things in life, I may not be able to resurrect it.

Cheers,

Joseph


Re: NVDA development course

hurrikennyandopo ...
 

Hi James


Joseph would be the person I think that set that group up. I just can not remember if it was for add ons and how to create them but I think it was documented.


There might be some places to look on this page at http://www.accessibilitycentral.net/NVDA%20screen%20reader%20related%20resources.html <http://www.accessibilitycentral.net/NVDA%20screen%20reader%20related%20resources.html>

I know there was a written tutorial by Joseph but can not seem to find it.


Maybe some of the other guides might help from off this page for add ons etc.


Gene nz

On 9/09/2021 10:51 pm, James AUSTIN wrote:
Hi gentle people

Hope everyone is well.

Back in 2019 I believe, a subgroup was created to discuss NVDA development. Would anyone by any chance please be willing to share in link to this information if it is available somewhere on the web as I am unable to find it.

Thank you

Kind regards

James




Re: Google Drive for Desktop Accessibility?

Vlad Dragomir
 

True about ppop-ups, we need to re-open the client from the systray each time that happens. For “Shared with me”, I usually go and use the web version, I had no idea there was such a tab in the client.


Re: Google Drive for Desktop Accessibility?

Aine Kelly Costello
 

I went okay with logging in and for me it automatically shows the folders for my drive and shared drives in file explorers. But I occasionally see pop-ups come up. There the focus with NVDA is really jumpy, and if you navigate away by changing windows you can't get back not even with object navigation, even when visually the dialogue is still there.
Also I can't figure out how to get other tabs particularly 'shared with me" (which isn't the same thing as shared rives) to show up.
But if you just want the syncing thing, you can dump everything in the My drive folder and it should work fine. 


Re: NVDA documentation

David Mellor
 

Hi Gene,
Browsing the objects provides different information than you get from NVDA-b.
Running it on an empty window for example I get told about controls like scroll bars, system menu, minimize and maximize for example.
In as far as the two methods cover similar information, it can require quite some attension to keep up with NVDA-b and lightning response to stop it at the correct point. You'd likely not be far off though for hierarchical navigation. I like to be able to browse one object at a time, like browsing a file line by line rather than with automatic read.
I agree that both are really useful.
Best wishes,
David
 


Re: Google Drive for Desktop Accessibility?

Ashley Wayne
 

I’m just trying to set it up lol.


On Thu, Sep 9, 2021, 9:04 AM Vlad Dragomir <vladdragomir1983@...> wrote:

Dear all,

 

I haven’t had any problems with the new client so far. I can modify the settings, I can read the upload progress, etc. Everything’s like a webpage. What are you trying to do? If I can help I’ll be happy to.

 

Cheers,

 

Vlad.


Re: Google Drive for Desktop Accessibility?

Vlad Dragomir
 

Dear all,

 

I haven’t had any problems with the new client so far. I can modify the settings, I can read the upload progress, etc. Everything’s like a webpage. What are you trying to do? If I can help I’ll be happy to.

 

Cheers,

 

Vlad.


Re: not constantly maintained addon and compatibility issue

 

On Thu, Sep 9, 2021 at 01:41 AM, William wrote:
Can we have a mechanism to make these addons being maintained, even if the developer ignored it or forget to update it?
-
You do realize that what you propose is a logical impossibility, don't you?

If all the necessary maintenance is amounts to doing what's proposed later, that is updating the manifest and doing testing with the current version of NVDA, then the developer (whether the original one or someone else) has updated what needs to be updated.

The problem is that there are some add-ons that have been abandoned by their original developer and have not, at least as yet, been picked up by someone else.  If and when they do, then that person or those persons will again be maintaining the add-on.

While I commend those willing to try editing the manifest files as a workaround, that's precisely what it is if no one is maintaining the actual code.  Eventually, a manifest tweak will not be enough.  Right now it is for certain add-ons, but that will not last as time marches on.  Someone else has to pick up maintenance on the code if it is to remain viable over the long term.
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 


Re: NVDA documentation

Gene
 

Not necessarily, or if it does, you first have to know they exist.  Because of the many objects and how you have to find and move into containing objects, you may well find objects you wouldn’t have found if you had looked manually. 
 
There are times when you might want to use control b and times when you will want to look manually but neither one is sufficient by itself in all circumstances.
 
Gene

-----Original Message-----
Sent: Thursday, September 09, 2021 9:46 AM
Subject: Re: [nvda] NVDA documentation
 
Thanks Gene.
I didn't know NVDA-b would select the object when stopped like that.
The facility to browse through the objects manually allows more careful consideration though. :)
David

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 09 September 2021 14:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA documentation

I meant NVDA b.  I’m not sure if that is the same thing as is being discussed but, if you are in object review, using that command moves through every object in the active window.  And if you stop when a certain object is being announced the object navigator will be on that object.
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 8:06 AM
Subject: Re: [nvda] NVDA documentation
 
NVDA+2 (main keyboard) toggles speaking of typed characters?
I'm not sure what you had in mind there Gene.
David
 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 09 September 2021 13:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA documentation

Is scrolling through all the objects the same thing as using NVDA key 2 on the main  keyboard? 
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


Re: NVDA documentation

David Mellor
 

Thanks Gene.
I didn't know NVDA-b would select the object when stopped like that.
The facility to browse through the objects manually allows more careful consideration though. :)
David


From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 09 September 2021 14:17
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA documentation

I meant NVDA b.  I’m not sure if that is the same thing as is being discussed but, if you are in object review, using that command moves through every object in the active window.  And if you stop when a certain object is being announced the object navigator will be on that object.
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 8:06 AM
Subject: Re: [nvda] NVDA documentation
 
NVDA+2 (main keyboard) toggles speaking of typed characters?
I'm not sure what you had in mind there Gene.
David
 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 09 September 2021 13:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA documentation

Is scrolling through all the objects the same thing as using NVDA key 2 on the main  keyboard? 
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


Re: not constantly maintained addon and compatibility issue

Roger Stewart
 

If you have a program like 7Zip, you can just open the archive which will let you see into the zip file without opening it. Then you can find the manifest.ini file and edit it and then save the changes and now you have an nvda add on with an updated manifest.ini file and you can then install it as long as it is really compatible with the new version of nvda.

Roger










On 9/9/2021 9:13 AM, Gene wrote:
As far as I know, you can’t install incompatible add-ons.  I get a message, before installation can proceed, that the add-on has been blocked because of incompatibility. 
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 9:10 AM
Subject: Re: [nvda] not constantly maintained addon and compatibility issue
 
hi,
if you have the addons installed, you just need to go to the NVDA configuration directory.
there you can find the addons folder.
In short, find the addon you want to edit the manifest file, enter the folder and edit the file using a text editor such as notepad.
good luck.
 
On Thu, Sep 9, 2021 at 3:55 PM William <xsuper.sillyx@...> wrote:

Well, do you mean rename the .addon file to .zip,

unzip it,

use text editor to open the .ini file

edit the line last tested version to thelatest nvda version

then zip the folder back to  a .zip file and rename to a .addon file?

 

Fawaz Abdul rahman 於 9/9/2021 17:10 寫道:

Hi,
if it is just a matter of the flag, then you can edit the manifest.ini file yourself and it should work properly.
However, if you are not sure how to do it or what to do, send the addons you have issues with, and someone may be able to help you.
good luck.
 
 
On Thu, Sep 9, 2021 at 8:41 AM William <xsuper.sillyx@...> wrote:
Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not
supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having
compatibility issue", it is only not updated the addon file to state
that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William









Re: not constantly maintained addon and compatibility issue

Gene
 

As far as I know, you can’t install incompatible add-ons.  I get a message, before installation can proceed, that the add-on has been blocked because of incompatibility. 
 
Gene

-----Original Message-----
Sent: Thursday, September 09, 2021 9:10 AM
Subject: Re: [nvda] not constantly maintained addon and compatibility issue
 
hi,
if you have the addons installed, you just need to go to the NVDA configuration directory.
there you can find the addons folder.
In short, find the addon you want to edit the manifest file, enter the folder and edit the file using a text editor such as notepad.
good luck.
 
On Thu, Sep 9, 2021 at 3:55 PM William <xsuper.sillyx@...> wrote:

Well, do you mean rename the .addon file to .zip,

unzip it,

use text editor to open the .ini file

edit the line last tested version to thelatest nvda version

then zip the folder back to  a .zip file and rename to a .addon file?

 

Fawaz Abdul rahman 於 9/9/2021 17:10 寫道:

Hi,
if it is just a matter of the flag, then you can edit the manifest.ini file yourself and it should work properly.
However, if you are not sure how to do it or what to do, send the addons you have issues with, and someone may be able to help you.
good luck.
 
 
On Thu, Sep 9, 2021 at 8:41 AM William <xsuper.sillyx@...> wrote:
Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not
supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having
compatibility issue", it is only not updated the addon file to state
that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William








Re: not constantly maintained addon and compatibility issue

Fawaz Abdul rahman
 

hi,
if you have the addons installed, you just need to go to the NVDA configuration directory.
there you can find the addons folder.
In short, find the addon you want to edit the manifest file, enter the folder and edit the file using a text editor such as notepad.
good luck.


On Thu, Sep 9, 2021 at 3:55 PM William <xsuper.sillyx@...> wrote:

Well, do you mean rename the .addon file to .zip,

unzip it,

use text editor to open the .ini file

edit the line last tested version to thelatest nvda version

then zip the folder back to  a .zip file and rename to a .addon file?


Fawaz Abdul rahman 於 9/9/2021 17:10 寫道:

Hi,
if it is just a matter of the flag, then you can edit the manifest.ini file yourself and it should work properly.
However, if you are not sure how to do it or what to do, send the addons you have issues with, and someone may be able to help you.
good luck.


On Thu, Sep 9, 2021 at 8:41 AM William <xsuper.sillyx@...> wrote:
Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not
supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having
compatibility issue", it is only not updated the addon file to state
that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William








Re: Google Drive for Desktop Accessibility?

Ashley Wayne
 

I have the same issues. I’ve used narrator on some of the screens but even that only partially works.


On Wed, Sep 8, 2021, 11:02 PM John Sanfilippo <johnsanfilippo@...> wrote:
Hi, I was a Backup and Sync user and, as is life's nature, things
changed. That's ok, but the new system appears to be no more accessible
than the old.

Is there any NVDA magic to get things working together? The stand
keyboard nav does not appear to work, nor do siple screen review
commands. Or, they wrk sporadically.

John


--
- JS o m -






Re: NVDA documentation

Gene
 

I meant NVDA b.  I’m not sure if that is the same thing as is being discussed but, if you are in object review, using that command moves through every object in the active window.  And if you stop when a certain object is being announced the object navigator will be on that object.
 
Gene

-----Original Message-----
Sent: Thursday, September 09, 2021 8:06 AM
Subject: Re: [nvda] NVDA documentation
 
NVDA+2 (main keyboard) toggles speaking of typed characters?
I'm not sure what you had in mind there Gene.
David
 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 09 September 2021 13:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA documentation

Is scrolling through all the objects the same thing as using NVDA key 2 on the main  keyboard? 
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


Re: NVDA documentation

David Mellor
 

NVDA+2 (main keyboard) toggles speaking of typed characters?
I'm not sure what you had in mind there Gene.
David



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Gene
Sent: 09 September 2021 13:25
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA documentation

Is scrolling through all the objects the same thing as using NVDA key 2 on the main  keyboard? 
 
Gene
-----Original Message-----
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


Re: not constantly maintained addon and compatibility issue

William
 

Well, do you mean rename the .addon file to .zip,

unzip it,

use text editor to open the .ini file

edit the line last tested version to thelatest nvda version

then zip the folder back to  a .zip file and rename to a .addon file?


Fawaz Abdul rahman 於 9/9/2021 17:10 寫道:

Hi,
if it is just a matter of the flag, then you can edit the manifest.ini file yourself and it should work properly.
However, if you are not sure how to do it or what to do, send the addons you have issues with, and someone may be able to help you.
good luck.


On Thu, Sep 9, 2021 at 8:41 AM William <xsuper.sillyx@...> wrote:
Hello, especially for nvda developers and addon developers,


Thanks to lots of addon that enhanced my productivity.

The current situation is that, some of the addon that I am using is not
supporting the latest nvda 2021.1 and are forced to be blocked by nvda.

To my understanding, some of these addons are not really "having
compatibility issue", it is only not updated the addon file to state
that the addon is supporting the latest nvda, am i right?


Can we have a mechanism to make these addons being maintained, even

if the developer ignored it or forget to update it?


Thanks,

William








Re: NVDA documentation

Gene
 

Is scrolling through all the objects the same thing as using NVDA key 2 on the main  keyboard? 
 
Gene

-----Original Message-----
Sent: Thursday, September 09, 2021 3:20 AM
Subject: Re: [nvda] NVDA documentation
 

Hi Quentin ,

I'm not too concerned with arguing the case for default key strokes being setup.

So long as it goes into the manual then people can set the keys up if they wish.

I think these functions can be very useful though. When using object navigation to find elements that we know are on the screen somewhere but may not have a clear sense of the object hierarchy it can be a lot easier if time consuming to just scroll through all of the objects.

I have certainly used this on occasion.

I've assigned them to 3 and 9, prev and next respectively.

Very best wishes,

David

 


NVDA development course

James AUSTIN
 

Hi gentle people

Hope everyone is well.

Back in 2019 I believe, a subgroup was created to discuss NVDA development. Would anyone by any chance please be willing to share in link to this information if it is available somewhere on the web as I am unable to find it.

Thank you

Kind regards

James

401 - 800 of 87797