Date   

Time zoner is not compatible wish NVDA 2021.1

Ján Kulik
 

Hello.

Will the NVDA time zone add-on be available in NVDA 2021.1? I'm looking for a contact for the author but I can't find him E-mail. If the author is reading this email, please let us know
-
Ján Kulik


Re: Miniaudible: request for accessibility.

Gabriele Battaglia
 

Reply to the Joseph Lee's message, wrote on 14/06/2021 at 19:43:
Hi,
Based on dev info, I wonder which version of QT is in use, as that could play a role in this scenario (I think).
Hi Joseph.
As soon as I get in touch with them I'll ask it.

Do you think is something we can do from the addon side?


Re: Miniaudible: request for accessibility.

Gabriele Battaglia
 

Reply to the Florian Beijers's message, wrote on 14/06/2021 at 19:39:
that there's also a window called " Virtual machine" which makes me
wonder if we are even looking at native controls or just some VM
working over RDP, VNC or similar?

Hi Florian.
The application, as I know by running it under MacOS, is a multitabbed editor. One is used to code, another one is an output only console and then you have a virtual machine in which the processes runs.
Virtual Machine is used as an output monitor too and it contains even graphical data while the console is text only, used typically for timing and error messages.

Gabe.


Re: Miniaudible: request for accessibility.

Gabriele Battaglia
 

Reply to the Luke Davis's message, wrote on 14/06/2021 at 19:36:
Have you contacted the developers of this, to find out if they are willing to work toward accessibility?
Yep Luke. I sent a couple of message to their mailinglist and sent a private mail to one of the author.
No answers back yet.
Gabe.


Re: Miniaudible: request for accessibility.

Gabriele Battaglia
 

Reply to the James Scholes's message, wrote on 14/06/2021 at 19:19:
Could you post the developer info (obtained via NVDA+F1) for a control within the application on Windows? That may give us some insights as to what technologies it's using that would make it accessible on the Mac, before somebody potentially downloads it to explore.
Hi James and thanks for interest.
I saw that they're already posted.
If you need additional info, just ask.
Gabe.


Re: Miniaudible: request for accessibility.

Florian Beijers
 

Can't immediately determine, no qt dlls in the program folder. Executables seem to be self-contained entirely, unfortunately.


Op ma 14 jun. 2021 om 19:43 schreef Joseph Lee <joseph.lee22590@...>:

Hi,
Based on dev info, I wonder which version of QT is in use, as that could play a role in this scenario (I think).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Florian Beijers
Sent: Monday, June 14, 2021 10:39 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Miniaudible: request for accessibility.

Hmm,

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(19:37:19.475) - MainThread (2752):
Developer info for navigator object:
name: None
role: ROLE_PANE
roleText: None
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.Dynamic_ClipboardCommandAnnouncementClientIAccessible
object at 0x0559E4B0>
Python class mro: (<class
'NVDAObjects.Dynamic_ClipboardCommandAnnouncementClientIAccessible'>,
<class 'globalPlugins.NVDAExtensionGlobalPlugin.clipboardCommandAnnouncement.ClipboardCommandAnnouncement'>,
<class 'NVDAObjects.IAccessible.qt.Client'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'garbageHandler.TrackedObject'>, <class 'object'>)
description: None
location: RectLTWH(left=2, top=152, width=1914, height=864)
value: None
appModule: <'appModuleHandler' (appName 'miniaudicle', process ID
34144) at address 9ebfe90>
appModule.productName: exception: No version information
appModule.productVersion: exception: No version information
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 922008
windowClassName: 'QWidget'
windowControlID: 0
windowStyle: -1748041728
extendedWindowStyle: 256
windowThreadID: 45680
windowText: 'miniAudicle'
displayText: ''
IAccessibleObject: <POINTER(IAccessible) ptr=0xe03fd70 at 9eb8e40>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=922008, objectID=-4, childID=-45 IAccessible accName: None IAccessible accRole: ROLE_SYSTEM_CLIENT IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580) IAccessible accDescription: None IAccessible accValue: None

NVDA reports "pane"  without any other info. The interesting thing is that there's also a window called " Virtual machine"  which makes me wonder if we are even looking at native controls or just some VM working over RDP, VNC or similar?

Florian

2021-06-14 19:19 GMT+02:00, James Scholes <james@...>:
> Could you post the developer info (obtained via NVDA+F1) for a control
> within the application on Windows?  That may give us some insights as
> to what technologies it's using that would make it accessible on the
> Mac, before somebody potentially downloads it to explore.
>
> Regards,
>
> James Scholes
>
> On 14/06/2021 at 9:41 am, Gabriele Battaglia via groups.io wrote:
>> Hello All.
>> I'm fascinating by a programming language objects oriented which is
>> specifically designed to create and manage sounds. It's a project
>> from a USA University.
>>
>> You can use it at 90% via command line but all its powerful must be
>> obtained throw its IDE which is a simple multitab text editor called
>> Miniaudible.
>> Unfortunately it is totally not accessible to NVDA.
>> The strangest thing is that under MacOS, it is.
>>
>> Is there anyone who can write an add-on for it? Or, does something
>> already exist?
>> The programming language is named Chuck:
>> http://chuck.stanford.edu
>>
>> Thanks.
>>
>> Gabe.
>>
>
>
>
>
>
>











Re: Miniaudible: request for accessibility.

 

Hi,
Based on dev info, I wonder which version of QT is in use, as that could play a role in this scenario (I think).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Florian Beijers
Sent: Monday, June 14, 2021 10:39 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Miniaudible: request for accessibility.

Hmm,

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(19:37:19.475) - MainThread (2752):
Developer info for navigator object:
name: None
role: ROLE_PANE
roleText: None
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.Dynamic_ClipboardCommandAnnouncementClientIAccessible
object at 0x0559E4B0>
Python class mro: (<class
'NVDAObjects.Dynamic_ClipboardCommandAnnouncementClientIAccessible'>,
<class 'globalPlugins.NVDAExtensionGlobalPlugin.clipboardCommandAnnouncement.ClipboardCommandAnnouncement'>,
<class 'NVDAObjects.IAccessible.qt.Client'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <class 'garbageHandler.TrackedObject'>, <class 'object'>)
description: None
location: RectLTWH(left=2, top=152, width=1914, height=864)
value: None
appModule: <'appModuleHandler' (appName 'miniaudicle', process ID
34144) at address 9ebfe90>
appModule.productName: exception: No version information
appModule.productVersion: exception: No version information
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 922008
windowClassName: 'QWidget'
windowControlID: 0
windowStyle: -1748041728
extendedWindowStyle: 256
windowThreadID: 45680
windowText: 'miniAudicle'
displayText: ''
IAccessibleObject: <POINTER(IAccessible) ptr=0xe03fd70 at 9eb8e40>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=922008, objectID=-4, childID=-45 IAccessible accName: None IAccessible accRole: ROLE_SYSTEM_CLIENT IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580) IAccessible accDescription: None IAccessible accValue: None

NVDA reports "pane" without any other info. The interesting thing is that there's also a window called " Virtual machine" which makes me wonder if we are even looking at native controls or just some VM working over RDP, VNC or similar?

Florian

2021-06-14 19:19 GMT+02:00, James Scholes <james@jls-radio.com>:
Could you post the developer info (obtained via NVDA+F1) for a control
within the application on Windows? That may give us some insights as
to what technologies it's using that would make it accessible on the
Mac, before somebody potentially downloads it to explore.

Regards,

James Scholes

On 14/06/2021 at 9:41 am, Gabriele Battaglia via groups.io wrote:
Hello All.
I'm fascinating by a programming language objects oriented which is
specifically designed to create and manage sounds. It's a project
from a USA University.

You can use it at 90% via command line but all its powerful must be
obtained throw its IDE which is a simple multitab text editor called
Miniaudible.
Unfortunately it is totally not accessible to NVDA.
The strangest thing is that under MacOS, it is.

Is there anyone who can write an add-on for it? Or, does something
already exist?
The programming language is named Chuck:
http://chuck.stanford.edu

Thanks.

Gabe.





Re: Miniaudible: request for accessibility.

Florian Beijers
 

Hmm,

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(19:37:19.475) - MainThread (2752):
Developer info for navigator object:
name: None
role: ROLE_PANE
roleText: None
states: STATE_FOCUSABLE, STATE_FOCUSED
isFocusable: True
hasFocus: True
Python object: <NVDAObjects.Dynamic_ClipboardCommandAnnouncementClientIAccessible
object at 0x0559E4B0>
Python class mro: (<class
'NVDAObjects.Dynamic_ClipboardCommandAnnouncementClientIAccessible'>,
<class 'globalPlugins.NVDAExtensionGlobalPlugin.clipboardCommandAnnouncement.ClipboardCommandAnnouncement'>,
<class 'NVDAObjects.IAccessible.qt.Client'>, <class
'NVDAObjects.IAccessible.IAccessible'>, <class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class
'baseObject.AutoPropertyObject'>, <class
'garbageHandler.TrackedObject'>, <class 'object'>)
description: None
location: RectLTWH(left=2, top=152, width=1914, height=864)
value: None
appModule: <'appModuleHandler' (appName 'miniaudicle', process ID
34144) at address 9ebfe90>
appModule.productName: exception: No version information
appModule.productVersion: exception: No version information
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 922008
windowClassName: 'QWidget'
windowControlID: 0
windowStyle: -1748041728
extendedWindowStyle: 256
windowThreadID: 45680
windowText: 'miniAudicle'
displayText: ''
IAccessibleObject: <POINTER(IAccessible) ptr=0xe03fd70 at 9eb8e40>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=922008, objectID=-4, childID=-45
IAccessible accName: None
IAccessible accRole: ROLE_SYSTEM_CLIENT
IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE,
STATE_SYSTEM_VALID (1048580)
IAccessible accDescription: None
IAccessible accValue: None

NVDA reports "pane" without any other info. The interesting thing is
that there's also a window called " Virtual machine" which makes me
wonder if we are even looking at native controls or just some VM
working over RDP, VNC or similar?

Florian

2021-06-14 19:19 GMT+02:00, James Scholes <james@jls-radio.com>:

Could you post the developer info (obtained via NVDA+F1) for a control
within the application on Windows? That may give us some insights as to
what technologies it's using that would make it accessible on the Mac,
before somebody potentially downloads it to explore.

Regards,

James Scholes

On 14/06/2021 at 9:41 am, Gabriele Battaglia via groups.io wrote:
Hello All.
I'm fascinating by a programming language objects oriented which is
specifically designed to create and manage sounds. It's a project from a
USA University.

You can use it at 90% via command line but all its powerful must be
obtained throw its IDE which is a simple multitab text editor called
Miniaudible.
Unfortunately it is totally not accessible to NVDA.
The strangest thing is that under MacOS, it is.

Is there anyone who can write an add-on for it? Or, does something
already exist?
The programming language is named Chuck:
http://chuck.stanford.edu

Thanks.

Gabe.





Re: Miniaudible: request for accessibility.

Luke Davis
 

Hello

Have you contacted the developers of this, to find out if they are willing to work toward accessibility?

Luke

Gabriele Battaglia via groups.io wrote:

Hello All.
I'm fascinating by a programming language objects oriented which is specifically designed to create and manage sounds. It's a project from a USA University.

You can use it at 90% via command line but all its powerful must be obtained throw its IDE which is a simple multitab text editor called Miniaudible.
Unfortunately it is totally not accessible to NVDA.
The strangest thing is that under MacOS, it is.

Is there anyone who can write an add-on for it? Or, does something already exist?
The programming language is named Chuck:
http://chuck.stanford.edu


Re: Miniaudible: request for accessibility.

James Scholes
 

Could you post the developer info (obtained via NVDA+F1) for a control within the application on Windows? That may give us some insights as to what technologies it's using that would make it accessible on the Mac, before somebody potentially downloads it to explore.

Regards,

James Scholes

On 14/06/2021 at 9:41 am, Gabriele Battaglia via groups.io wrote:
Hello All.
I'm fascinating by a programming language objects oriented which is
specifically designed to create and manage sounds. It's a project from a
USA University.

You can use it at 90% via command line but all its powerful must be
obtained throw its IDE which is a simple multitab text editor called
Miniaudible.
Unfortunately it is totally not accessible to NVDA.
The strangest thing is that under MacOS, it is.

Is there anyone who can write an add-on for it? Or, does something
already exist?
The programming language is named Chuck:
http://chuck.stanford.edu

Thanks.

Gabe.


Miniaudible: request for accessibility.

Gabriele Battaglia
 

Hello All.
I'm fascinating by a programming language objects oriented which is specifically designed to create and manage sounds. It's a project from a USA University.

You can use it at 90% via command line but all its powerful must be obtained throw its IDE which is a simple multitab text editor called Miniaudible.
Unfortunately it is totally not accessible to NVDA.
The strangest thing is that under MacOS, it is.

Is there anyone who can write an add-on for it? Or, does something already exist?
The programming language is named Chuck:
http://chuck.stanford.edu

Thanks.

Gabe.
--
Gabriele Battaglia, IZ4APU (Libero)
Sent from TB on Windows 10, Genus Bononiae's computer.


Re: Weather_Plus8.0 bug risolto

Adriano Barbieri
 

You're right Luke,thanks, I'm aware of it, but for that little bug, I didn't think it necessary to change the version number as I just published it, with all the consequent changes to manifest file and so on.
Best regards
Adriano


Il 11/06/2021 23:43, Luke Davis ha scritto:

Adriano

It is considered a bad idea to release different versions with the same version number.

Now if anyone reports a bug with 8.0, you have to ask them exactly when, and in what timezone, they downloaded it, in order to be sure that they are using the latest version of 8.0. That is the whole thing that version numbers exist to prevent.

If you are following semantic versioning for this add-on (https://semver.org), which I think you might be, then this could have been done as 8.0.1.

Luke

 Adriano Barbieri via groups.io wrote:

Fixed the repetition of the Weather_Plus preferences menu

Download it again:
https: //www.nvda.it/files/plugin/weather_plus8.0.nvda-addon
Now it's okay, sorry.
Thanks and keep sending me feedback, the changes were massive and I was expecting some minor bugs.






Windows Magnifier 1.0

Cyrille
 

Hello

Windows Magnifier first stable release has just been published.
Direct download link:

http://github.com/CyrilleB79/winMag/releases/download/V1.0/winMag-1.0.nvda-addon

The request (PR) has already been made to have this release available on the community website and through add-on updater.

Thanks to all testers of the dev version for their feedback during the test phase.

Cheers,

Cyrille
 


Re: Non working add ons

 

any news about bluetooth audio addon?
even that doesnt work with latest version.

On 6/14/21, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
Regarding Add-on Updater and incompatible add-ons, apart from the
workaround
I described earlier, a change is being planned that will prevent Add-on
Updater from fetching incompatible add-ons - a combination of client side
9Add-on Updater) and server side (add-on metadata) changes.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Brian's Mail list account via groups.io
Sent: Monday, June 14, 2021 12:23 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Non working add ons

I just like the stereo feature, since it does make more sense to me than
some of the other add-ons that do just replace words with sounds. Each to
their own, but that is me.
If I update to these trial versions I presumably need to turn uff updates
or add on updater tries to downdate them as it does with toolbar explorer
and other add ons.
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.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Cagri Dogan" <cagrid@hotmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Sunday, June 13, 2021 4:03 PM
Subject: Re: [nvda-addons] Non working add ons


Hi rui,
For audiothemes addon revised by you, checking or leaving unchecked "Speak
roles such as button, edit box , link etc." Makes no difference. The main
motivation for my preference to use this addon was to hear sounds instead
of

the names of the controls.
All the best, Çağrı
Windows 10 için Posta<https://go.microsoft.com/fwlink/?LinkId=550986> ile
gönderildi

Kimden: Rui Fontes<mailto:rui.fontes@tiflotecnia.com>
Gönderilme: 13 Haziran 2021 Pazar 17:06
Kime:
nvda-addons@nvda-addons.groups.io<mailto:nvda-addons@nvda-addons.groups.io>
Konu: Re: [nvda-addons] Non working add ons

Hello!


systrayList is now maintained by me.

Last version, compatible with NVDA 2021.1, is awaiting aproval by
NVAccess, after prevvious aproval by Noelia, and is available at:

https://github.com/ruifontes/systrayList/releases/download/21.06/systrayList
-21.06.nvda-addon


Regarding audioThemes3D, you can get a working version adapted by me at:

https://www.dropbox.com/s/lrivy4cir54d1iv/audiothemes_6.0_Gen.nvda-addon?dl=
1


Best regards,


Rui Fontes



Às 09:25 de 13/06/2021, Brian's Mail list account via groups.io escreveu:
At the moment there are two add ons that do not work with the latest
versions, both the beta and alpha. These are, for me at least.
Sound schemes, ie the 3D playing of sounds for events.
and
Systray list. A very handy little item to give confidence that a tray
icon exists and has not been obliterated by a badly behaved tray
display. Intel are you reading this!


Does anyone know if these are being actively looked at?

I am also noting that I'm being prompted in the beta at the moment for
add-on updates that are not appropriate, ie Goldwave latest when the
old one is my best working version for the older version of that
software, and Toolbar explorer,which I have a dev version of that
works but it keeps on wanting to install the stable version and then
says its not compatible and gives up.
Weird.
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.
Newsgroup monitored: alt.comp.blind-users
























--
to listen to the Blind Android Users Podcast visit.
www.blindandroidusers.com
To join our mailing list, send those “join requests” to:
blindandroidusers+subscribe@groups.io
You may follow us on twitter using our handle:
@BlindDroidUsers
https://twitter.com/@BlindDroidUsers
We do have a Telegram group that you can join and share stories or
whatever with our members at:
https://t.me/ANATAD


Re: Non working add ons

 

Hi,
Regarding Add-on Updater and incompatible add-ons, apart from the workaround
I described earlier, a change is being planned that will prevent Add-on
Updater from fetching incompatible add-ons - a combination of client side
9Add-on Updater) and server side (add-on metadata) changes.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Brian's Mail list account via groups.io
Sent: Monday, June 14, 2021 12:23 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Non working add ons

I just like the stereo feature, since it does make more sense to me than
some of the other add-ons that do just replace words with sounds. Each to
their own, but that is me.
If I update to these trial versions I presumably need to turn uff updates
or add on updater tries to downdate them as it does with toolbar explorer
and other add ons.
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.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Cagri Dogan" <cagrid@hotmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Sunday, June 13, 2021 4:03 PM
Subject: Re: [nvda-addons] Non working add ons


Hi rui,
For audiothemes addon revised by you, checking or leaving unchecked "Speak
roles such as button, edit box , link etc." Makes no difference. The main
motivation for my preference to use this addon was to hear sounds instead of

the names of the controls.
All the best, Çağrı
Windows 10 için Posta<https://go.microsoft.com/fwlink/?LinkId=550986> ile
gönderildi

Kimden: Rui Fontes<mailto:rui.fontes@tiflotecnia.com>
Gönderilme: 13 Haziran 2021 Pazar 17:06
Kime:
nvda-addons@nvda-addons.groups.io<mailto:nvda-addons@nvda-addons.groups.io>
Konu: Re: [nvda-addons] Non working add ons

Hello!


systrayList is now maintained by me.

Last version, compatible with NVDA 2021.1, is awaiting aproval by
NVAccess, after prevvious aproval by Noelia, and is available at:

https://github.com/ruifontes/systrayList/releases/download/21.06/systrayList
-21.06.nvda-addon


Regarding audioThemes3D, you can get a working version adapted by me at:

https://www.dropbox.com/s/lrivy4cir54d1iv/audiothemes_6.0_Gen.nvda-addon?dl=
1


Best regards,


Rui Fontes



Às 09:25 de 13/06/2021, Brian's Mail list account via groups.io escreveu:
At the moment there are two add ons that do not work with the latest
versions, both the beta and alpha. These are, for me at least.
Sound schemes, ie the 3D playing of sounds for events.
and
Systray list. A very handy little item to give confidence that a tray
icon exists and has not been obliterated by a badly behaved tray
display. Intel are you reading this!


Does anyone know if these are being actively looked at?

I am also noting that I'm being prompted in the beta at the moment for
add-on updates that are not appropriate, ie Goldwave latest when the
old one is my best working version for the older version of that
software, and Toolbar explorer,which I have a dev version of that
works but it keeps on wanting to install the stable version and then
says its not compatible and gives up.
Weird.
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.
Newsgroup monitored: alt.comp.blind-users





Re: Non working add ons

Brian's Mail list account
 

I just like the stereo feature, since it does make more sense to me than some of the other add-ons that do just replace words with sounds. Each to their own, but that is me.
If I update to these trial versions I presumably need to turn uff updates or add on updater tries to downdate them as it does with toolbar explorer and other add ons.
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.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Cagri Dogan" <cagrid@hotmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Sunday, June 13, 2021 4:03 PM
Subject: Re: [nvda-addons] Non working add ons


Hi rui,
For audiothemes addon revised by you, checking or leaving unchecked “Speak roles such as button, edit box , link etc.” Makes no difference. The main motivation for my preference to use this addon was to hear sounds instead of the names of the controls.
All the best, Çağrı
Windows 10 için Posta<https://go.microsoft.com/fwlink/?LinkId=550986> ile gönderildi

Kimden: Rui Fontes<mailto:rui.fontes@tiflotecnia.com>
Gönderilme: 13 Haziran 2021 Pazar 17:06
Kime: nvda-addons@nvda-addons.groups.io<mailto:nvda-addons@nvda-addons.groups.io>
Konu: Re: [nvda-addons] Non working add ons

Hello!


systrayList is now maintained by me.

Last version, compatible with NVDA 2021.1, is awaiting aproval by
NVAccess, after prevvious aproval by Noelia, and is available at:

https://github.com/ruifontes/systrayList/releases/download/21.06/systrayList-21.06.nvda-addon


Regarding audioThemes3D, you can get a working version adapted by me at:

https://www.dropbox.com/s/lrivy4cir54d1iv/audiothemes_6.0_Gen.nvda-addon?dl=1


Best regards,


Rui Fontes



Às 09:25 de 13/06/2021, Brian's Mail list account via groups.io escreveu:
At the moment there are two add ons that do not work with the latest
versions, both the beta and alpha. These are, for me at least.
Sound schemes, ie the 3D playing of sounds for events.
and
Systray list. A very handy little item to give confidence that a tray
icon exists and has not been obliterated by a badly behaved tray
display. Intel are you reading this!


Does anyone know if these are being actively looked at?

I am also noting that I'm being prompted in the beta at the moment for
add-on updates that are not appropriate, ie Goldwave latest when the
old one is my best working version for the older version of that
software, and Toolbar explorer,which I have a dev version of that
works but it keeps on wanting to install the stable version and then
says its not compatible and gives up.
Weird.
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.
Newsgroup monitored: alt.comp.blind-users





Re: readFeeds compatible with NVDA 2021.1

Noelia Ruiz
 

Hello:
Luke wrote:
If I am correct about this code, if there are valid files in RSS and personalFeeds, only the ones in personalFeeds will ever be copied.
The ones in RSS will be ignored.

Answer: No, valid files contained in personalFeeds and RSS subfolders
(included in the user configuration directory) will be copied.

You can test it placing different files in both subfolders and
installing this version of the add-on.

Something else to consider: because these are copy operations, unless
this is handled somewhere else, won't this have to run again and again
on the same old files, any time the add-on is installed or updated?
Shouldn't it be moving the old files, or deleting them after copy
(without passing on the IOError, of course).

This is just an option to restore important files that the user can
save if desired. It's documented in the readme: the add-on have two
options, one for copying (saving important) feeds, and the other one
to restore them. So, we can copy feeds to be restored later when we
want, and therefore the feeds offered to be copied at installation
won't be always the same feeds.

Please, if you haven't do it, read the documentation and feel free to
improve it creating an issue or a PR at

https://github.com/nvdaes/readFeeds




2021-06-13 21:28 GMT+02:00, Luke Davis <luke@newanswertech.com>:
Noelia

I still have the same questions, which are not answered by the update.
That is, you fixed the one bug, but I think this is hiding two others.
Maybe, but I am still not sure what is intended here.

Can somebody else take a look at this and verify whether I am
misunderstanding something?

In the code block:

addonPath = [os.path.join(CONFIG_PATH, "RSS"),
os.path.join(CONFIG_PATH, "personalFeeds")]
shouldOfferRestoreBackup = False
for path in addonPath:
if not os.path.isdir(path):
continue
pathFiles = os.listdir(path)
validFiles = glob.glob(path + "\\*.txt")
if len(pathFiles) != len(validFiles):
continue
shouldOfferRestoreBackup = True

If I am correct about this code, if there are valid files in RSS and
personalFeeds, only the ones in personalFeeds will ever be copied.

The ones in RSS will be ignored.

Is that intended?

I explained in my other message why that will happen.

Something else to consider: because these are copy operations, unless this
is handled somewhere else, won't this have to run again and again on the
same old files, any time the add-on is installed or updated?
Shouldn't it be moving the old files, or deleting them after copy (without
passing on the IOError, of course).

Luke





Noelia Ruiz wrote:

Hello:

Thanks all people who has contributed this topic. The code was
intended to do what it does in version 10.2, but now it's improved. It
should be fixed in

https://github.com/nvdaes/readFeeds/pull/17

I have decided not to mention this improvement in the log due to the
complexity of the explanation and since now, by default, the folder
where feeds can be copied, by default, is personalFeeds. RSS was a
folder used long time ago.





Add-on Updater June 14th try build, updates to JSON metadata

 

Hi all,

Add-on Updater June 14th try build is now available:

https://github.com/josephsl/addonUpdater/releases/download/21.05.1/addonUpdater-20210614-dev.nvda-addon

 

Also, the add-ons metadata JSON file was updated:

  • A new dictionary named “general” was added to record information such as last modified date, current backwards incompatible API release and other metadata about add-ons metadata. This dictionary is mostly intended for tools and should not be edited by humans unless needed.
  • Renamed “active” dictionary to “stable” dictionary to record the fact that this dictionary records info on stable add-ons. This name isn’t final – it can change without notice.

 

Ideas under consideration:

  • Update channels: a list of available update channels. If implemented, it will be accompanied by a possibility of defining different versions for different channels. For most add-ons, stable channel will do but there are add-ons with dedicated dev channel releases.
  • Version: a dedicated “version” key will be added to JSON file for use by tools. This should resolve a problem where add-on version isn’t obvious from add-on installer filename.

 

Thanks.

Cheers,

Joseph


Re: Fork in Github

Luke Davis
 

Javi Domínguez wrote:

https://github.com/nvda-es/updateChannel/
Interesting. I find the fork button just fine there, although for me the releases link is missing.
I'm not really concerned about that one, because GitHub links have a tendency to come and go, only being definitely there when GitHub thinks you should see them.

Fortunately all of their stuff can be reached by common-sense endpoints.

Luke


Re: readFeeds compatible with NVDA 2021.1

Luke Davis
 

Noelia

I still have the same questions, which are not answered by the update.
That is, you fixed the one bug, but I think this is hiding two others.
Maybe, but I am still not sure what is intended here.

Can somebody else take a look at this and verify whether I am misunderstanding something?

In the code block:

addonPath = [os.path.join(CONFIG_PATH, "RSS"), os.path.join(CONFIG_PATH, "personalFeeds")]
shouldOfferRestoreBackup = False
for path in addonPath:
if not os.path.isdir(path):
continue
pathFiles = os.listdir(path)
validFiles = glob.glob(path + "\\*.txt")
if len(pathFiles) != len(validFiles):
continue
shouldOfferRestoreBackup = True

If I am correct about this code, if there are valid files in RSS and personalFeeds, only the ones in personalFeeds will ever be copied.

The ones in RSS will be ignored.

Is that intended?

I explained in my other message why that will happen.

Something else to consider: because these are copy operations, unless this is handled somewhere else, won't this have to run again and again on the same old files, any time the add-on is installed or updated?
Shouldn't it be moving the old files, or deleting them after copy (without passing on the IOError, of course).

Luke





Noelia Ruiz wrote:

Hello:

Thanks all people who has contributed this topic. The code was
intended to do what it does in version 10.2, but now it's improved. It
should be fixed in

https://github.com/nvdaes/readFeeds/pull/17

I have decided not to mention this improvement in the log due to the
complexity of the explanation and since now, by default, the folder
where feeds can be copied, by default, is personalFeeds. RSS was a
folder used long time ago.

821 - 840 of 16478