Date   
Re: changing mainfests of nvda addons

Zachary Morris
 

Hello,

Thanks rui. But what if those fields are not there in the manifests file as mentioned?

On 5/6/2019 3:48 PM, Rui Fontes wrote:
Hello!
1 - Unzip the addon, or open it with 7ZIP;
2 - Change those fields in manifest.ini;
3 - Compact again or allow 7ZIP to update the ZIP file...

Rui Fontes


Às 14:35 de 06/05/2019, Zachary Morris escreveu:
Hello,

How to you change the minimum required nvda version and last tested nvda version? I am using one of the threshold snapshots and I was just wondering on how to do this.

Re: changing mainfests of nvda addons

 

Hi,
There is an under the surface problem that is masked by manifest edits: exactly what add-ons are affected? Because if you are using Threshold snapshots, you are effectively saying, "I'm willing to test backwards incompatible changes once they are ready". Hence, I think it would be best to contact authors of affected add-ons instead of editing manifests.
Cheers,
joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Zachary Morris
Sent: Monday, May 6, 2019 2:08 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] changing mainfests of nvda addons

Hello,

Thanks rui. But what if those fields are not there in the manifests file as mentioned?


On 5/6/2019 3:48 PM, Rui Fontes wrote:
Hello!
1 - Unzip the addon, or open it with 7ZIP;
2 - Change those fields in manifest.ini;
3 - Compact again or allow 7ZIP to update the ZIP file...

Rui Fontes


Às 14:35 de 06/05/2019, Zachary Morris escreveu:
Hello,

How to you change the minimum required nvda version and last tested
nvda version? I am using one of the threshold snapshots and I was
just wondering on how to do this.


Re: changing mainfests of nvda addons

Zachary Morris
 

Hello,

Ok, thanks Joseph.

On 5/6/2019 4:15 PM, Joseph Lee wrote:
Hi,
There is an under the surface problem that is masked by manifest edits: exactly what add-ons are affected? Because if you are using Threshold snapshots, you are effectively saying, "I'm willing to test backwards incompatible changes once they are ready". Hence, I think it would be best to contact authors of affected add-ons instead of editing manifests.
Cheers,
joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Zachary Morris
Sent: Monday, May 6, 2019 2:08 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] changing mainfests of nvda addons

Hello,

Thanks rui. But what if those fields are not there in the manifests file as mentioned?


On 5/6/2019 3:48 PM, Rui Fontes wrote:
Hello!
1 - Unzip the addon, or open it with 7ZIP;
2 - Change those fields in manifest.ini;
3 - Compact again or allow 7ZIP to update the ZIP file...

Rui Fontes


Às 14:35 de 06/05/2019, Zachary Morris escreveu:
Hello,

How to you change the minimum required nvda version and last tested
nvda version? I am using one of the threshold snapshots and I was
just wondering on how to do this.



Re: changing mainfests of nvda addons

Brian's Mail list account
 

Or if like me you just want to see what happens when you allow existing add ons to be accepted, note this can be dangerous, but I'm sure you know that, Then open up, say a portable version of nvda threshold with add ons installed. go to the user config and add ons folder and have a look at the manifest file of, say Josephs add onupdater. Look at the last few lines which have the earliest and latest versions of nvda listed, there is also another line that says whether only stable releases are looked for and in some min windows version as well. The whole lot can be cut and pasted into a text file and simply cut and pasted onto the manifest file of any other add on in the list in that folder.


Brian.


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

----- Original Message -----
From: "Rui Fontes" <rui.fontes@...>
To: <nvda-devel@groups.io>
Sent: Monday, May 06, 2019 9:48 PM
Subject: Re: [nvda-devel] changing mainfests of nvda addons


Hello!
1 - Unzip the addon, or open it with 7ZIP;
2 - Change those fields in manifest.ini;
3 - Compact again or allow 7ZIP to update the ZIP file...

Rui Fontes


Às 14:35 de 06/05/2019, Zachary Morris escreveu:
Hello,

How to you change the minimum required nvda version and last tested nvda version? I am using one of the threshold snapshots and I was just wondering on how to do this.

Re: changing mainfests of nvda addons

Brian's Mail list account
 

Yes, but many may not be a problem when problems do show up you can attempt to contact the author. I think one of the main things that needs to happen is for whoever contacts the author to be prepared for them to say, making it python 3 compatible is too much work. at that point one also needs to ask them if they might be prepared to donate the whole project to the community so others with more knowledge can have a go at the conversion.

So far the only one that definitely is going to give issues is the 3D sounds add on. If there is an alternative that can do this stereo and sound change bit then I'd get it and use it, but its not obvious to me from a quick scan of the add ons list.


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" <@joslee>
To: <nvda-devel@groups.io>
Sent: Monday, May 06, 2019 10:15 PM
Subject: Re: [nvda-devel] changing mainfests of nvda addons


Hi,
There is an under the surface problem that is masked by manifest edits: exactly what add-ons are affected? Because if you are using Threshold snapshots, you are effectively saying, "I'm willing to test backwards incompatible changes once they are ready". Hence, I think it would be best to contact authors of affected add-ons instead of editing manifests.
Cheers,
joseph

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Zachary Morris
Sent: Monday, May 6, 2019 2:08 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] changing mainfests of nvda addons

Hello,

Thanks rui. But what if those fields are not there in the manifests file as mentioned?


On 5/6/2019 3:48 PM, Rui Fontes wrote:
Hello!
1 - Unzip the addon, or open it with 7ZIP;
2 - Change those fields in manifest.ini;
3 - Compact again or allow 7ZIP to update the ZIP file...

Rui Fontes


Às 14:35 de 06/05/2019, Zachary Morris escreveu:
Hello,

How to you change the minimum required nvda version and last tested
nvda version? I am using one of the threshold snapshots and I was
just wondering on how to do this.


Latest beta restarting itself multiple times

Brian's Mail list account
 

When I installed this new snapshot over the current stable release as a portable then as well as some errors the nvda tones and hence nvda must have rebooted itself at least eight times before it settled down. Its now working. Is this an intentional thing, ie checking add ons one aat a time or something?
Just weird. Note worth a ticket really.
Windows 7 pro 64.
Brian

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

Re: Latest beta restarting itself multiple times

Brian's Mail list account
 

PS, However just uninstalled put the other back and did it again, and of course it all worked perfectly, bah humbug!
Brian

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

----- Original Message -----
From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Tuesday, May 07, 2019 8:46 AM
Subject: [nvda-devel] Latest beta restarting itself multiple times


When I installed this new snapshot over the current stable release as a portable then as well as some errors the nvda tones and hence nvda must have rebooted itself at least eight times before it settled down. Its now working. Is this an intentional thing, ie checking add ons one aat a time or something?
Just weird. Note worth a ticket really.
Windows 7 pro 64.
Brian

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

Re: How to view the debug logs, and get exceptions in NVDAHelper

Reef Turner
 

>   Does it end up in NVDA.log,

Yes, I THINK so. It's been a while since I did this myself and I'm not 100% sure. Have you tried this and not been able to see your log messages? If so, I suggest that you look for a message that is already in the log (coming from NVDA helper) and modify it to prove to yourself that it is indeed coming from nvda helper, and that your edits are showing up.

On Mon, 6 May 2019 at 17:19, derek riemer <driemer.riemer@...> wrote:
Where do debug logs go? Does it end up in NVDA.log, or elsewhere?

On Mon, May 6, 2019 at 7:18 AM Reef Turner <reef@...> wrote:
In addition to building NVDA with `nvdaHelperDebugFlags` (I'd suggest with debugCRT and RTC), you can also specify `nvdaHelperLogLevel=0` for maximum logging verbosity.

These args are defined in the `sconstruct` file.

On Sun, 28 Apr 2019 at 23:16, derek riemer <driemer.riemer@...> wrote:
I'm trying to get exceptions in NVDAHelper, for some error I caused in one of the MSHTML vbuff backend methods. 
I see this coder in remoteLoader/loader.cpp.
#ifndef NDEBUG
    Beep(880,100);
    #endif
I also see a logger method that does some cryptic things I don't understand. Does anyone here know how I can set the log level, and/or view the logs? How can I get a debugger attached to IE, so I can figure out what horrible thing I did that is crashing IE? I tried getting windbg to attach to iexplore but it won't do anything for some reason.
Short of that, can I generate a minidump somehow, or a full dump, when IE breaks? It doesn't seem to crash the whole browser, but just the page.
Chbeers
--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com






--
Reef Turner
Software Developer 
 




--
Derek Riemer
Improving the world one byte at a time!        ⠠⠊⠍⠏⠗⠕⠧⠬ ⠮ ⠸⠺ ⠐⠕ ⠃⠽⠞⠑ ⠁⠞ ⠁ ⠐⠞⠖
•    Accessibility enthusiast.
•    Proud user of the NVDA screen reader.
•    Open source enthusiast.
•    Skier.

•    Personal website: https://derekriemer.com






--
Reef Turner
Software Developer 
 


Re: Questions about NVDA objects

francisco del roio
 

Hello,

El 31/3/2019 a las 10:51, francisco del roio escribió:
Hello,

What's happen with NVDA objects? Are they recreated for all events or
cached somewhere? What about it's relation with particular handlers?

Developer guide says all about app modules, overlay classes and object
instantiation, but nothing about object life cycle.

Are there any documentation about this particular thing?

Cheers,
Anything about this particular thing?

Thanks again.
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: Latest beta restarting itself multiple times

Brian's Mail list account
 

I think this may well have something to do with my old problem of locked files. Some work has been done on how logs are generated I think, which might have affected timings.
Incidentally sometimes after accepting an update the update dialogue comes back again and one needs to shift tab to get to the install dialogue.
This is on all versions but not all the time.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: <nvda-devel@groups.io>
Sent: Tuesday, May 07, 2019 9:11 AM
Subject: Re: [nvda-devel] Latest beta restarting itself multiple times


PS, However just uninstalled put the other back and did it again, and of course it all worked perfectly, bah humbug!
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Brian's Mail list account via Groups.Io" <bglists=blueyonder.co.uk@groups.io>
To: "NVDA Dev list on groups.io" <nvda-devel@groups.io>
Sent: Tuesday, May 07, 2019 8:46 AM
Subject: [nvda-devel] Latest beta restarting itself multiple times


When I installed this new snapshot over the current stable release as a portable then as well as some errors the nvda tones and hence nvda must have rebooted itself at least eight times before it settled down. Its now working. Is this an intentional thing, ie checking add ons one aat a time or something?
Just weird. Note worth a ticket really.
Windows 7 pro 64.
Brian

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



Eset products not working

francisco del roio
 

Dear NVDA developers,

I have a problem. NVDA doesn't read the user interface of eset products,
at least internet security.
See this log chunk:

```
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.328):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:44.349):
Speaking [u'ESET Internet Security']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.355):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:44.375):
Speaking [u'desconocido']
IO - speech.speak (07:34:44.377):
Speaking [u'desconocido']
IO - inputCore.InputManager.executeGesture (07:34:44.691):
Input: kb(desktop):tab
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.701):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.713):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:44.717):
Speaking [u'desconocido']
IO - inputCore.InputManager.executeGesture (07:34:44.993):
Input: kb(desktop):tab
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:45.009):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:45.016):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:45.019):
Speaking [u'desconocido']
IO - inputCore.InputManager.executeGesture (07:34:45.788):
Input: kb(desktop):NVDA+f1
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:45.792):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(07:34:45.891):
Developer info for navigator object:
name: None
role: ROLE_UNKNOWN
states:
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.IAccessible.IAccessible object at 0x04CA88F0>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>, <class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: None
value: None
appModule: <'appModuleHandler' (appName 'egui', process ID 11308) at
address 48ca8d0>
appModule.productName: u'ESET Security'
appModule.productVersion: u'12.1.34.0'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 197498
windowClassName: u'EsetBaseWindow'
windowControlID: 0
windowStyle: 1442906112
extendedWindowStyle: 0
windowThreadID: 10620
windowText: u''
displayText: exception: 'NoneType' object is not iterable
IAccessibleObject: <POINTER(IAccessible) ptr=0x6f5c1a0 at 4d4e2b0>
IAccessibleChildID: -1893059533
IAccessible event parameters: windowHandle=197498, objectID=-4,
childID=-1893059533
IAccessible accName: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
IAccessible accRole: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
IAccessible accState: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
IAccessible accDescription: exception: (-2147024809, 'El par\xe1metro no
es correcto.', (None, None, None, 0, None))
IAccessible accValue: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
```

I wrote to Eset support and they told me that their products are
prepared to work with screen readers. I've tested with JAWS (I have a
demo version installed just for these things) and it works.

Is there a solution? Where can I begin to investigate this? (assuming
you cannot review this for now).

I'm asking because I don't know the IAccessible API.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Re: Eset products not working

Brian's Mail list account
 

The thing is that Jaws has still got a video interceptor and this may be why it works. I think perhaps the company are not up to date perhaps.

I've not tried it myself, but I've yet to find an anti virus package where everything works, since often they block hooking in from outside in case its some attempt to compromise the anti virus system.
Only the Microsoft one seems ok, though one can sort of use superantispyware and the like if you use screen and global navigation.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
Sent: Friday, May 10, 2019 12:22 PM
Subject: Eset products not working


Dear NVDA developers,

I have a problem. NVDA doesn't read the user interface of eset products,
at least internet security.
See this log chunk:

```
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.328):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:44.349):
Speaking [u'ESET Internet Security']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.355):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:44.375):
Speaking [u'desconocido']
IO - speech.speak (07:34:44.377):
Speaking [u'desconocido']
IO - inputCore.InputManager.executeGesture (07:34:44.691):
Input: kb(desktop):tab
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.701):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:44.713):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:44.717):
Speaking [u'desconocido']
IO - inputCore.InputManager.executeGesture (07:34:44.993):
Input: kb(desktop):tab
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:45.009):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:45.016):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
IO - speech.speak (07:34:45.019):
Speaking [u'desconocido']
IO - inputCore.InputManager.executeGesture (07:34:45.788):
Input: kb(desktop):NVDA+f1
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(07:34:45.792):
accRole failed: (-2147024809, 'El par\xe1metro no es correcto.', (None,
None, None, 0, None))
INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(07:34:45.891):
Developer info for navigator object:
name: None
role: ROLE_UNKNOWN
states:
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.IAccessible.IAccessible object at 0x04CA88F0>
Python class mro: (<class 'NVDAObjects.IAccessible.IAccessible'>, <class
'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class
'documentBase.TextContainerObject'>, <class
'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>,
<type 'object'>)
description: None
location: None
value: None
appModule: <'appModuleHandler' (appName 'egui', process ID 11308) at
address 48ca8d0>
appModule.productName: u'ESET Security'
appModule.productVersion: u'12.1.34.0'
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 197498
windowClassName: u'EsetBaseWindow'
windowControlID: 0
windowStyle: 1442906112
extendedWindowStyle: 0
windowThreadID: 10620
windowText: u''
displayText: exception: 'NoneType' object is not iterable
IAccessibleObject: <POINTER(IAccessible) ptr=0x6f5c1a0 at 4d4e2b0>
IAccessibleChildID: -1893059533
IAccessible event parameters: windowHandle=197498, objectID=-4,
childID=-1893059533
IAccessible accName: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
IAccessible accRole: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
IAccessible accState: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
IAccessible accDescription: exception: (-2147024809, 'El par\xe1metro no
es correcto.', (None, None, None, 0, None))
IAccessible accValue: exception: (-2147024809, 'El par\xe1metro no es
correcto.', (None, None, None, 0, None))
```

I wrote to Eset support and they told me that their products are
prepared to work with screen readers. I've tested with JAWS (I have a
demo version installed just for these things) and it works.

Is there a solution? Where can I begin to investigate this? (assuming
you cannot review this for now).

I'm asking because I don't know the IAccessible API.

Cheers,
--
Cuando tus fuerzas terminan, las de mi Dios comienzan.

Spellink error in whats new in alpha snap.

Brian's Mail list account
 

. In Scintilla controls such as Noteplad++, NVDA can read the correct line when wordwrap is ...

noteplad?
Brian


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

Re: Spellink error in whats new in alpha snap.

Reef Turner
 

Thanks Brian, this has now been corrected.


On Fri, 10 May 2019 at 20:40, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
. In Scintilla controls such as Noteplad++, NVDA can read the correct line
when wordwrap is ...

noteplad?
 Brian


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users






--
Reef Turner
Software Developer 
 


Re: Spellink error in whats new in alpha snap.

Brian's Mail list account
 

Yes finally found the time to report it officially, seems to have been too much life going on round here of late.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Reef Turner" <reef@...>
To: <nvda-devel@groups.io>
Sent: Monday, May 13, 2019 11:10 AM
Subject: Re: [nvda-devel] Spellink error in whats new in alpha snap.


Thanks Brian, this has now been corrected.

On Fri, 10 May 2019 at 20:40, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:

. In Scintilla controls such as Noteplad++, NVDA can read the correct line
when wordwrap is ...

noteplad?
Brian


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users




--
Reef Turner
Software Developer

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


Add-on development guide: let us remove the one found on add-ons community website in favor of GitHub version

 

Hi all,

 

Some of you may see this message up to three times – that’s the beauty and a curse of blind carbon copies.

 

There was a question raised on the add-ons list regarding where to find the add-on development guide. At the moment the one that appears from Google search is:

https://addons.nvda-project.org/devDocs/devDocs.en.html

 

However, the most up-to-date version can be found here:

https://github.com/nvdaaddons/DevGuide/wiki/NVDA-Add-on-Development-Guide

 

I propose that we start referring to the second link. Although the first one has been translated into several languages, it is very out of date, as the last revision was in 2016 and hasn’t been updated ever since and won’t be updated at all. Although the second one is very up to date, it hasn’t been translated yet (personally I prefer to keep the guide in English, but I’m open to other possibilities). The biggest advantage of the second one is support for tables, and the fact that this is a wiki document that is also ready for revisions through Git make it a more attractive option.

 

Note that even though I am the author of the add-on development guide, it is still subject to community-based revisions. Also, Project Threshold is slowly being planned, which will make the first link obsolete. Therefore, you are more than welcome to provide feedback as to what to do until a few days after Threshold is launched, at which point backwards incompatible changes from my side (in this case, the link for the add-on development guide) will be locked.

 

Thank you.

Cheers,

Joseph

Re: Add-on development guide: let us remove the one found on add-ons community website in favor of GitHub version

Tage Johansson
 

Hi,


I agree with you. It is only confusing to have two addon development guides, and I was actually confused myself the first time I googled which one to pick.


If someone really want to translate it then they can of course do that, but I think it is better to have an up to date guide in english than an out dated in many languages.


Best regards,

Tage


On 5/14/2019 12:55 AM, Joseph Lee wrote:

Hi all,

 

Some of you may see this message up to three times – that’s the beauty and a curse of blind carbon copies.

 

There was a question raised on the add-ons list regarding where to find the add-on development guide. At the moment the one that appears from Google search is:

https://addons.nvda-project.org/devDocs/devDocs.en.html

 

However, the most up-to-date version can be found here:

https://github.com/nvdaaddons/DevGuide/wiki/NVDA-Add-on-Development-Guide

 

I propose that we start referring to the second link. Although the first one has been translated into several languages, it is very out of date, as the last revision was in 2016 and hasn’t been updated ever since and won’t be updated at all. Although the second one is very up to date, it hasn’t been translated yet (personally I prefer to keep the guide in English, but I’m open to other possibilities). The biggest advantage of the second one is support for tables, and the fact that this is a wiki document that is also ready for revisions through Git make it a more attractive option.

 

Note that even though I am the author of the add-on development guide, it is still subject to community-based revisions. Also, Project Threshold is slowly being planned, which will make the first link obsolete. Therefore, you are more than welcome to provide feedback as to what to do until a few days after Threshold is launched, at which point backwards incompatible changes from my side (in this case, the link for the add-on development guide) will be locked.

 

Thank you.

Cheers,

Joseph

Re: Add-on development guide: let us remove the one found on add-ons community website in favor of GitHub version

Brian's Mail list account
 

Re the translations. Are there any parts of the guide that remain unchanged and could have their translations, say in a zip download somewhere should any prospective translators come along later.
Having said all that, it is going to be a very difficult task to keep such a document up to date even in one language, let lone several.
This is a not just a problem on nvda but on many projects where users can add to the functionality etc.
I directly am not going to use it, but if I do meet anyone who is pretty good at programming just having one place for resources generally will be easier to pass on to them I feel.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <@joslee>
To: <nvda-devel@groups.io>
Sent: Monday, May 13, 2019 11:55 PM
Subject: [nvda-devel] Add-on development guide: let us remove the one found on add-ons community website in favor of GitHub version


Hi all,



Some of you may see this message up to three times - that's the beauty and a
curse of blind carbon copies.



There was a question raised on the add-ons list regarding where to find the
add-on development guide. At the moment the one that appears from Google
search is:

https://addons.nvda-project.org/devDocs/devDocs.en.html



However, the most up-to-date version can be found here:

https://github.com/nvdaaddons/DevGuide/wiki/NVDA-Add-on-Development-Guide



I propose that we start referring to the second link. Although the first one
has been translated into several languages, it is very out of date, as the
last revision was in 2016 and hasn't been updated ever since and won't be
updated at all. Although the second one is very up to date, it hasn't been
translated yet (personally I prefer to keep the guide in English, but I'm
open to other possibilities). The biggest advantage of the second one is
support for tables, and the fact that this is a wiki document that is also
ready for revisions through Git make it a more attractive option.



Note that even though I am the author of the add-on development guide, it is
still subject to community-based revisions. Also, Project Threshold is
slowly being planned, which will make the first link obsolete. Therefore,
you are more than welcome to provide feedback as to what to do until a few
days after Threshold is launched, at which point backwards incompatible
changes from my side (in this case, the link for the add-on development
guide) will be locked.



Thank you.

Cheers,

Joseph



Re: Add-on development guide: let us remove the one found on add-ons community website in favor of GitHub version

Jim Homme
 

Hi,

How do we get this to happen? I also think that some parts of the Development Guide from NVAccess should go in this area. The content from NVAccess would help beginning add-on developers get started.

 

Jim

 

 

 

==========

Jim Homme

Digital Accessibility

Bender Consulting Services

412-787-8567

https://www.benderconsult.com/our%20services/hightest-accessible-technology-solutions

 

From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Tage Johansson via Groups.Io
Sent: Monday, May 13, 2019 11:49 PM
To: nvda-devel@groups.io
Subject: Re: [nvda-devel] Add-on development guide: let us remove the one found on add-ons community website in favor of GitHub version

 

Hi,

 

I agree with you. It is only confusing to have two addon development guides, and I was actually confused myself the first time I googled which one to pick.

 

If someone really want to translate it then they can of course do that, but I think it is better to have an up to date guide in english than an out dated in many languages.

 

Best regards,

Tage

 

On 5/14/2019 12:55 AM, Joseph Lee wrote:

Hi all,

 

Some of you may see this message up to three times – that’s the beauty and a curse of blind carbon copies.

 

There was a question raised on the add-ons list regarding where to find the add-on development guide. At the moment the one that appears from Google search is:

https://addons.nvda-project.org/devDocs/devDocs.en.html

 

However, the most up-to-date version can be found here:

https://github.com/nvdaaddons/DevGuide/wiki/NVDA-Add-on-Development-Guide

 

I propose that we start referring to the second link. Although the first one has been translated into several languages, it is very out of date, as the last revision was in 2016 and hasn’t been updated ever since and won’t be updated at all. Although the second one is very up to date, it hasn’t been translated yet (personally I prefer to keep the guide in English, but I’m open to other possibilities). The biggest advantage of the second one is support for tables, and the fact that this is a wiki document that is also ready for revisions through Git make it a more attractive option.

 

Note that even though I am the author of the add-on development guide, it is still subject to community-based revisions. Also, Project Threshold is slowly being planned, which will make the first link obsolete. Therefore, you are more than welcome to provide feedback as to what to do until a few days after Threshold is launched, at which point backwards incompatible changes from my side (in this case, the link for the add-on development guide) will be locked.

 

Thank you.

Cheers,

Joseph

Introducing our Google Summer of Code 2019 student: Bill Dengler

Michael Curran
 

Hi all,


On behalf of NV Access I would like to officially welcome Bill Dengler (codeofdusk) to the NVDA project, as our Google Summer of Code 2019 student.


Many people may have already seen Bill around, as he has contributed to the project in the past. But we are very happy to be working with him in an official capacity, under the Google Summer of Code program.


Between now and the end of August, Bill will be working on improving NVDA's support for Windows consoles in Windows 10, by having NVDA take advantage of UI Automation in this scenario.


You can read about NV Access on Google Summer of Code, plus Bill's project abstract at https://summerofcode.withgoogle.com/organizations/5317267756154880/


Please join me in making Bill welcome.


Regards

Mick