Date   

Re: problems with Notepad ++ addon

Brian's Mail list account
 

I'm not on that list these days.
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: "Mr. Wong Chi Wai, William" <cwwong.pro@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, August 21, 2019 1:26 PM
Subject: Re: [nvda-addons] problems with Notepad ++ addon


Yes, the reason has been discussed on NVDA mailing list and its a long story that cannot be covered here.




Brian's Mail list account via Groups.Io 於 21/8/2019 18:17 寫道:
Is there a reason not to use the latest nvda stable version?
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: "Mr. Wong Chi Wai, William" <cwwong.pro@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, August 21, 2019 11:07 AM
Subject: [nvda-addons] problems with Notepad ++ addon


Hi all,
Win 7, NVDA 2019.1.1, latest Notepad++32bit

I tried using the newly posted Notepad ++ addon, and came across the following issues:
1.
When I first installed the addon, it displayed something like "this addon cannot be installed"
Although this msg is showed, the addon can be found under the manage addon page, and the addon is found to be active.
I hope to reproduce the problem by uninstalling the addon and reinstall it again, but the second time it didn't produce that error msg.

2. \
According to the description,
Support for the Previous/Next Find Feature
By Default, if you press control+f you bring up the find dialog. If you type text here and press enter, the text in the window is selected and the document is moved to the next search result. In Notepad++ you can press f3 or shift+f3 to repeat the search in the forward or backward direction respectively. NVDA will read both the current line, and the selection within the line which represents the found text.

I tried the search by pressing ctrl f, searching something and press enter
then I pressed f3 or shift f3 and NVDA didn't speak anything about the match result

Thanks,
William






Re: Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)

 

Hi,

At least I’m fully conscious to respond to this…

One route for resource leaks is import side-effects – while importing an add-on, the add-on code may load something that is volatile such as a resource online. Once the add-on closes unexpectedly (and without a terminate method being defined), the add-on would not release the resource cleanly.

As for this being an add-on: I advise holding off on that, as things might change in 20H1 that could make this unnecessary.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via Groups.Io
Sent: Wednesday, August 21, 2019 4:54 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re : Re: [nvda-addons] Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)

 

Hello Luke

Thank you for your detailed feedback.

First, note that my goal was to make a quick workaround (firstly for my onw usage), not to fix the issue. I do not yet have installed the environment to run NVDA from source and thus will not propose a PR for NVDA core. I agree that exiting NVDA at first stage of startup (just after config reading) would be cleaner. If you or anyone else want to make such a PR, just feel free.

Regarding Joseph's comments:

In current implementation of this script, NVDA does not handle the wx.GetApp().ExitMainLoop command at global plugin's initialization (__init__) but in first core cycle after NVDA initialization has completed thanks to core.callLater. For me, it seems not different from what would happen if the user calls Exit NVDA command from the UI. Therefore, there should not be any problem such as resource not released, cleaned or freed. I do not understand so well the use case of the shutdown routine patch. However, I guess that should not be a problem either since full init has been performed and wx.GetApp().ExitMainLoop is called at a moment when the user may have called this command himself by a UI action (Exit command in NVDA menu). The addon's terminate methods should be called the same way, either NVDA's exit request comes from the script or from a user request via UI.

Of course, as told before, I am aware that letting NVDA complete its initialization to execute a shutdown command is not the most optimized solution but it does the job for my needs.

Regarding your feedbacks:

1. Logging the action of this script/addon at info level : I fully agree with you and will add it.

2. Change name and pack it as an addon. I do not understand why this would change since NVDA full initialization is performed anyway, regardless scripts' and addons' loading order, as explaned earlier. Anyway I may have missed something. I can perform this packaging and renaming if needed.

Let me know if something is wrong in my comments, or if you plan to do the PR for NVDA's core. Thanks.

Cheers,

Cyrille

----- Mail d'origine -----
De: Luke Davis <luke@...>
À: nvda-addons@nvda-addons.groups.io
Envoyé: Wed, 21 Aug 2019 00:46:46 +0200 (CEST)
Objet: Re: [nvda-addons] Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)

Hi Cyrille

Tested and confirmed to work properly *on my system* in NVDA 2019.2 beta.
But note, that is only properly on my own system. See below for why that may not
always be true, and why this is probably a bad idea.

First, a couple thoughts:

I very strongly suggest that you have this log something at info level about
what it's doing. At the moment, there is no evidence in the log that it even
exists, and I consider that a major bug.

Furthermore, I wonder if you could get it to run sooner, by renaming it with a
name that sorts first in the add-on load process
("000startupOptionWorkaround.py", for example), and packaging it as an add-on,
even for your own use, so it is not subject to scratchpad loading, which
appears to be a late load.

Now, all of that said:

Joseph Lee and I talked about this back in July, and he convinced me that doing
it via globalPlugin was a bad idea. The best method would be to do it in core,
right after config data is read in, but before anything really important
happens.

Here was his reasoning (posted with permission):

"
As for an add-on solution, very risky. Imagine an add-on that loads before
this one and performs something users may need to know, and then the
proposed add-on comes in and closes NVDA if NVDA is told to not start for
this user. If the previous add-on was holding onto a resource that isn't
cleaned up properly, that'll result in leaks. Or imagine an add-on that was
previously loaded that somehow patches the shutdown routine. If that
happens, NVDA will get confused when the proposed add-on unexpectedly
terminates NVDA.
"

Luke
On Tue, 20 Aug 2019, Cyrille via Groups.Io wrote:

>
> Hello
>
>  
>
> If NVDA starts after logon even if disabled following Win 10 1903 update, here is a work around script :
>
> https://raw.githubusercontent.com/CyrilleB79/NVDAScripts/master/globalPlugins/startupOptionWorkaround.py
>
> This script needs to be copied in the scratchpad\globalPlugins directory after having active the scratchpad option (if required).
>
> This script does not fixes the issue but unloads NVDA if it was not configured to start after logon.
>
> Feedback welcomed although it is a “quick dirty script”.
>
> I do not plan to release it as an addon, unless there is a demand.
>
>  
>
> Cheers
>
>  
>
> Cyrille
>
>  
>
>  
>
>  
>
> De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Cyrille via Groups.Io
> Envoyé : lundi 19 août 2019 17:56
> À : nvda-addons@nvda-addons.groups.io
> Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
>
>  
>
> Hello
>
>  
>
> @Jaffar
>
> Reading the ticket, I have understood that :
>
> * The issue occurs only if NVDA is activated on logon screen (seems not to be your case)
> * Seems to impact only some computers, not all
>
> @Joseph
>
> Thank you for this information, that you also wrote in the ticket.
>
> Since the fix will not be provided by MS before 2020, I intend to develop this workaround so that my wife does not have to quit NVDA (or forget to do it)
> each time she starts her session.
>
>  
>
> Seems that I still just need to figure if current NVDA version was run with the --ease-of-access flag. Is there an internal variable for it ? Or should I
> deal with NVDA process command line ?
>
>  
>
> Thanks.
>
> Cheers,
>
>  
>
> Cyrille
>
>  
>
>  
>
> *  
>
>  
>
> De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Jaffar Sidek
> Envoyé : lundi 19 août 2019 17:38
> À : nvda-addons@nvda-addons.groups.io
> Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
>
>  
>
> Hi.  My copy of NVDA running on Windows 10 1903 is not subject to this fault.  It might be that I have Jaws running as the default startup screen reader,
> but as of now, NVDA will not start on my desktop unless I explicitly tell it to do so with the usual alt+ctrl+n.  Cheers!
>
> On 8/19/2019 11:22 PM, Joseph Lee wrote:
>
> Hi,
>
> Microsoft is looking into this, and I hope it can be resolved in 20H1 (next year) as 19H2 (the next feature update) is going through testing at
> the moment.
>
> Cheers,
>
> Joseph
>
>  
>
> From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via Groups.Io
> Sent: Monday, August 19, 2019 8:20 AM
> To: nvda-addons@nvda-addons.groups.io
> Subject: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
>
>  
>
> Hello all
>
>  
>
> Following the Windows 10 1903 update, NVDA is started after all session startup, regardless wether the corresponding option is checked or not in NVDA
> settings.
>
> This problem is described in the following ticket :
>
> On Windows 10 1903 NVDA starts after logon even when this is disabled #9528
>
> This ticket tells us that this issue should be corrected by Microsoft but not so soon, it seems.
>
>  
>
> Has any one of you developed or planned to develop an addon, a simple script or implemented another work-around in NVDA or out of it ?
>
>  
>
> If no, I would plan to make a script or addon to unload NVDA if the option is not checked and if NVDA was run with the –easeofaccess flag. Just not so
> sure to have time so soon ; I do not know if this would take me much time or not.
>
>  
>
> Any feedkback, hint or better idea welcome !
>
>  
>
> Cheers,
>
>  
>
> Cyrille
>
>  
>
>
>
>


Re: problems with Notepad ++ addon

Andy B.
 

Did you try the 64bit version of notepad++? I didn't have any of those problems...

Latest notepad++ x64, NVDA 2019.2, latest notepad++ add-on, Windows 10 (1903/next).

On 8/21/2019 8:26 AM, Mr. Wong Chi Wai, William wrote:
Yes, the reason has been discussed on NVDA mailing list and its a long story that cannot be covered here.




Brian's Mail list account via Groups.Io 於 21/8/2019 18:17 寫道:
Is there a reason not to use the latest nvda stable version?
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: "Mr. Wong Chi Wai, William" <cwwong.pro@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, August 21, 2019 11:07 AM
Subject: [nvda-addons] problems with Notepad ++ addon


Hi all,
Win 7, NVDA 2019.1.1, latest Notepad++32bit

I tried using the newly posted Notepad ++ addon, and came across the following issues:
1.
When I first installed the addon, it displayed something like "this addon cannot be installed"
Although this msg is showed, the addon can be found under the manage addon page, and the addon is found to be active.
I hope to reproduce the problem by uninstalling the addon and reinstall it again, but the second time it didn't produce that error msg.

2. \
According to the description,
Support for the Previous/Next Find Feature
By Default, if you press control+f you bring up the find dialog. If you type text here and press enter, the text in the window is selected and the document is moved to the next search result. In Notepad++ you can press f3 or shift+f3 to repeat the search in the forward or backward direction respectively. NVDA will read both the current line, and the selection within the line which represents the found text.

I tried the search by pressing ctrl f, searching something and press enter
 then I pressed f3 or shift f3 and NVDA didn't speak anything about the match result

Thanks,
William







Re: problems with Notepad ++ addon

Mr. Wong Chi Wai, William <cwwong.pro@...>
 

Yes, the reason has been discussed on NVDA mailing list and its a long story that cannot be covered here.




Brian's Mail list account via Groups.Io 於 21/8/2019 18:17 寫道:

Is there a reason not to use the latest nvda stable version?
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: "Mr. Wong Chi Wai, William" <cwwong.pro@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, August 21, 2019 11:07 AM
Subject: [nvda-addons] problems with Notepad ++ addon


Hi all,
Win 7, NVDA 2019.1.1, latest Notepad++32bit

I tried using the newly posted Notepad ++ addon, and came across the following issues:
1.
When I first installed the addon, it displayed something like "this addon cannot be installed"
Although this msg is showed, the addon can be found under the manage addon page, and the addon is found to be active.
I hope to reproduce the problem by uninstalling the addon and reinstall it again, but the second time it didn't produce that error msg.

2. \
According to the description,
Support for the Previous/Next Find Feature
By Default, if you press control+f you bring up the find dialog. If you type text here and press enter, the text in the window is selected and the document is moved to the next search result. In Notepad++ you can press f3 or shift+f3 to repeat the search in the forward or backward direction respectively. NVDA will read both the current line, and the selection within the line which represents the found text.

I tried the search by pressing ctrl f, searching something and press enter
 then I pressed f3 or shift f3 and NVDA didn't speak anything about the match result

Thanks,
William





Re : Re: [nvda-addons] Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)

Cyrille
 

Hello Luke
Thank you for your detailed feedback.
First, note that my goal was to make a quick workaround (firstly for my onw usage), not to fix the issue. I do not yet have installed the environment to run NVDA from source and thus will not propose a PR for NVDA core. I agree that exiting NVDA at first stage of startup (just after config reading) would be cleaner. If you or anyone else want to make such a PR, just feel free.
Regarding Joseph's comments:
In current implementation of this script, NVDA does not handle the wx.GetApp().ExitMainLoop command at global plugin's initialization (__init__) but in first core cycle after NVDA initialization has completed thanks to core.callLater. For me, it seems not different from what would happen if the user calls Exit NVDA command from the UI. Therefore, there should not be any problem such as resource not released, cleaned or freed. I do not understand so well the use case of the shutdown routine patch. However, I guess that should not be a problem either since full init has been performed and wx.GetApp().ExitMainLoop is called at a moment when the user may have called this command himself by a UI action (Exit command in NVDA menu). The addon's terminate methods should be called the same way, either NVDA's exit request comes from the script or from a user request via UI.
Of course, as told before, I am aware that letting NVDA complete its initialization to execute a shutdown command is not the most optimized solution but it does the job for my needs.
Regarding your feedbacks:
1. Logging the action of this script/addon at info level : I fully agree with you and will add it.
2. Change name and pack it as an addon. I do not understand why this would change since NVDA full initialization is performed anyway, regardless scripts' and addons' loading order, as explaned earlier. Anyway I may have missed something. I can perform this packaging and renaming if needed.
Let me know if something is wrong in my comments, or if you plan to do the PR for NVDA's core. Thanks.
Cheers,
Cyrille
----- Mail d'origine -----
De: Luke Davis <luke@...>
À: nvda-addons@nvda-addons.groups.io
Envoyé: Wed, 21 Aug 2019 00:46:46 +0200 (CEST)
Objet: Re: [nvda-addons] Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)
Hi Cyrille
Tested and confirmed to work properly *on my system* in NVDA 2019.2 beta.
But note, that is only properly on my own system. See below for why that may not
always be true, and why this is probably a bad idea.
First, a couple thoughts:
I very strongly suggest that you have this log something at info level about
what it's doing. At the moment, there is no evidence in the log that it even
exists, and I consider that a major bug.
Furthermore, I wonder if you could get it to run sooner, by renaming it with a
name that sorts first in the add-on load process
("000startupOptionWorkaround.py", for example), and packaging it as an add-on,
even for your own use, so it is not subject to scratchpad loading, which
appears to be a late load.
Now, all of that said:
Joseph Lee and I talked about this back in July, and he convinced me that doing
it via globalPlugin was a bad idea. The best method would be to do it in core,
right after config data is read in, but before anything really important
happens.
Here was his reasoning (posted with permission):
"
As for an add-on solution, very risky. Imagine an add-on that loads before
this one and performs something users may need to know, and then the
proposed add-on comes in and closes NVDA if NVDA is told to not start for
this user. If the previous add-on was holding onto a resource that isn't
cleaned up properly, that'll result in leaks. Or imagine an add-on that was
previously loaded that somehow patches the shutdown routine. If that
happens, NVDA will get confused when the proposed add-on unexpectedly
terminates NVDA.
"
Luke

On Tue, 20 Aug 2019, Cyrille via Groups.Io wrote:
>
> Hello
>
>  
>
> If NVDA starts after logon even if disabled following Win 10 1903 update, here is a work around script :
>
> https://raw.githubusercontent.com/CyrilleB79/NVDAScripts/master/globalPlugins/startupOptionWorkaround.py
>
> This script needs to be copied in the scratchpad\globalPlugins directory after having active the scratchpad option (if required).
>
> This script does not fixes the issue but unloads NVDA if it was not configured to start after logon.
>
> Feedback welcomed although it is a “quick dirty script”.
>
> I do not plan to release it as an addon, unless there is a demand.
>
>  
>
> Cheers
>
>  
>
> Cyrille
>
>  
>
>  
>
>  
>
> De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Cyrille via Groups.Io
> Envoyé : lundi 19 août 2019 17:56
> À : nvda-addons@nvda-addons.groups.io
> Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
>
>  
>
> Hello
>
>  
>
> @Jaffar
>
> Reading the ticket, I have understood that :
>
> * The issue occurs only if NVDA is activated on logon screen (seems not to be your case)
> * Seems to impact only some computers, not all
>
> @Joseph
>
> Thank you for this information, that you also wrote in the ticket.
>
> Since the fix will not be provided by MS before 2020, I intend to develop this workaround so that my wife does not have to quit NVDA (or forget to do it)
> each time she starts her session.
>
>  
>
> Seems that I still just need to figure if current NVDA version was run with the --ease-of-access flag. Is there an internal variable for it ? Or should I
> deal with NVDA process command line ?
>
>  
>
> Thanks.
>
> Cheers,
>
>  
>
> Cyrille
>
>  
>
>  
>
> *  
>
>  
>
> De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Jaffar Sidek
> Envoyé : lundi 19 août 2019 17:38
> À : nvda-addons@nvda-addons.groups.io
> Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
>
>  
>
> Hi.  My copy of NVDA running on Windows 10 1903 is not subject to this fault.  It might be that I have Jaws running as the default startup screen reader,
> but as of now, NVDA will not start on my desktop unless I explicitly tell it to do so with the usual alt+ctrl+n.  Cheers!
>
> On 8/19/2019 11:22 PM, Joseph Lee wrote:
>
> Hi,
>
> Microsoft is looking into this, and I hope it can be resolved in 20H1 (next year) as 19H2 (the next feature update) is going through testing at
> the moment.
>
> Cheers,
>
> Joseph
>
>  
>
> From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via Groups.Io
> Sent: Monday, August 19, 2019 8:20 AM
> To: nvda-addons@nvda-addons.groups.io
> Subject: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
>
>  
>
> Hello all
>
>  
>
> Following the Windows 10 1903 update, NVDA is started after all session startup, regardless wether the corresponding option is checked or not in NVDA
> settings.
>
> This problem is described in the following ticket :
>
> On Windows 10 1903 NVDA starts after logon even when this is disabled #9528
>
> This ticket tells us that this issue should be corrected by Microsoft but not so soon, it seems.
>
>  
>
> Has any one of you developed or planned to develop an addon, a simple script or implemented another work-around in NVDA or out of it ?
>
>  
>
> If no, I would plan to make a script or addon to unload NVDA if the option is not checked and if NVDA was run with the –easeofaccess flag. Just not so
> sure to have time so soon ; I do not know if this would take me much time or not.
>
>  
>
> Any feedkback, hint or better idea welcome !
>
>  
>
> Cheers,
>
>  
>
> Cyrille
>
>  
>
>
>
>


Re: problems with Notepad ++ addon

Brian's Mail list account
 

Is there a reason not to use the latest nvda stable version?
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: "Mr. Wong Chi Wai, William" <cwwong.pro@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Wednesday, August 21, 2019 11:07 AM
Subject: [nvda-addons] problems with Notepad ++ addon


Hi all,
Win 7, NVDA 2019.1.1, latest Notepad++32bit

I tried using the newly posted Notepad ++ addon, and came across the following issues:
1.
When I first installed the addon, it displayed something like "this addon cannot be installed"
Although this msg is showed, the addon can be found under the manage addon page, and the addon is found to be active.
I hope to reproduce the problem by uninstalling the addon and reinstall it again, but the second time it didn't produce that error msg.

2. \
According to the description,
Support for the Previous/Next Find Feature
By Default, if you press control+f you bring up the find dialog. If you type text here and press enter, the text in the window is selected and the document is moved to the next search result. In Notepad++ you can press f3 or shift+f3 to repeat the search in the forward or backward direction respectively. NVDA will read both the current line, and the selection within the line which represents the found text.

I tried the search by pressing ctrl f, searching something and press enter
then I pressed f3 or shift f3 and NVDA didn't speak anything about the match result

Thanks,
William



problems with Notepad ++ addon

Mr. Wong Chi Wai, William <cwwong.pro@...>
 

Hi all,
Win 7, NVDA 2019.1.1, latest Notepad++32bit

I tried using the newly posted Notepad ++ addon, and came across the following issues:
1.
When I first installed the addon, it displayed something like "this addon cannot be installed"
Although this msg is showed, the addon can be found under the manage addon page, and the addon is found to be active.
I hope to reproduce the problem by uninstalling the addon and reinstall it again, but the second time it didn't produce that error msg.

2. \
According to the description,
Support for the Previous/Next Find Feature
By Default, if you press control+f you bring up the find dialog. If you type text here and press enter, the text in the window is selected and the document is moved to the next search result. In Notepad++ you can press f3 or shift+f3 to repeat the search in the forward or backward direction respectively. NVDA will read both the current line, and the selection within the line which represents the found text.

I tried the search by pressing ctrl f, searching something and press enter
 then I pressed f3 or shift f3 and NVDA didn't speak anything about the match result

Thanks,
William


Re: Unicode Braille Input: Merging in translations

 

Hey Noelia,


Thanks a lot for your info, this is certainly going to help me. Having access to that server doesn't seem necessary to me at this point.


Regards,
Leonard

Op 21-8-2019 om 10:04 schreef Noelia Ruiz:

Hi, the translations are merged from Assembla into the stable branch of the Bitbucket repo for the addon team account. You have to add this remote,  fetch and merge into your stable branch on GitHub. When I come back from holliday I can give you more help if you need it.
Usually, I merge translations and then I release a new minor version of add-ons. You The translations system was created by Mesar Hameed, who created the first guidelines and review process for add-ons, contributed by people like Jamie, Joseph and so on. The system was stored firstly on Bitbucket, in a previous existing account for addons and Nvda. Later Nvda was moved to GitHub. This uses mr config and Exbi server. I have access to this server to register addons and include then in the translations system, since Mesar wanted to show me how to do this firstly on his own server, and later he requested Jamie to grant me this access. You may request access to this server if you dont have, since you are a very active developer of Nvda.
Cheers

Enviado desde mi iPhone

El 21 ago 2019, a las 7:33, Leonard de Ruijter <alderuijter@...> escribió:

Hey All,


As I'm fairly new to add-on development, I have a quick question. What would be the quickest way to merge in translation updates for Unicode Braille Input into the development repository?


Cheers,

Leonard


Re: Unicode Braille Input: Merging in translations

Noelia Ruiz
 

Hi, the translations are merged from Assembla into the stable branch of the Bitbucket repo for the addon team account. You have to add this remote,  fetch and merge into your stable branch on GitHub. When I come back from holliday I can give you more help if you need it.
Usually, I merge translations and then I release a new minor version of add-ons. You The translations system was created by Mesar Hameed, who created the first guidelines and review process for add-ons, contributed by people like Jamie, Joseph and so on. The system was stored firstly on Bitbucket, in a previous existing account for addons and Nvda. Later Nvda was moved to GitHub. This uses mr config and Exbi server. I have access to this server to register addons and include then in the translations system, since Mesar wanted to show me how to do this firstly on his own server, and later he requested Jamie to grant me this access. You may request access to this server if you dont have, since you are a very active developer of Nvda.
Cheers

Enviado desde mi iPhone

El 21 ago 2019, a las 7:33, Leonard de Ruijter <alderuijter@...> escribió:

Hey All,


As I'm fairly new to add-on development, I have a quick question. What would be the quickest way to merge in translation updates for Unicode Braille Input into the development repository?


Cheers,

Leonard


Unicode Braille Input: Merging in translations

 

Hey All,


As I'm fairly new to add-on development, I have a quick question. What would be the quickest way to merge in translation updates for Unicode Braille Input into the development repository?


Cheers,

Leonard


Re: Welcome to the NVDA Community Add-ons website - Notepad++ #feed

Mr. Wong Chi Wai, William <cwwong.pro@...>
 

Hi
According to the page,
Support for the Previous/Next Find Feature
By Default, if you press control+f you bring up the find dialog. If you type text here and press enter, the text in the window is selected and the document is moved to the next search result. In Notepad++ you can press f3 or shift+f3 to repeat the search in the forward or backward direction respectively. NVDA will read both the current line, and the selection within the line which represents the found text.

I tested out and pressing f3 doesn't report anything by nvda.
nvda-addons@nvda-addons.groups.io Integration 於 20/8/2019 22:08 寫道:

Notepad++

This addon improves the accessibility of the notepad++ text editor. To learn more, and to read the documentation before installation, visit the addons github page



Re: Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)

Luke Davis
 

Hi Cyrille

Tested and confirmed to work properly *on my system* in NVDA 2019.2 beta.
But note, that is only properly on my own system. See below for why that may not always be true, and why this is probably a bad idea.

First, a couple thoughts:

I very strongly suggest that you have this log something at info level about what it's doing. At the moment, there is no evidence in the log that it even exists, and I consider that a major bug.

Furthermore, I wonder if you could get it to run sooner, by renaming it with a name that sorts first in the add-on load process ("000startupOptionWorkaround.py", for example), and packaging it as an add-on, even for your own use, so it is not subject to scratchpad loading, which appears to be a late load.

Now, all of that said:

Joseph Lee and I talked about this back in July, and he convinced me that doing it via globalPlugin was a bad idea. The best method would be to do it in core, right after config data is read in, but before anything really important happens.

Here was his reasoning (posted with permission):

"
As for an add-on solution, very risky. Imagine an add-on that loads before
this one and performs something users may need to know, and then the
proposed add-on comes in and closes NVDA if NVDA is told to not start for
this user. If the previous add-on was holding onto a resource that isn't
cleaned up properly, that'll result in leaks. Or imagine an add-on that was
previously loaded that somehow patches the shutdown routine. If that
happens, NVDA will get confused when the proposed add-on unexpectedly
terminates NVDA.
"

Luke

On Tue, 20 Aug 2019, Cyrille via Groups.Io wrote:

Hello
 
If NVDA starts after logon even if disabled following Win 10 1903 update, here is a work around script :
https://raw.githubusercontent.com/CyrilleB79/NVDAScripts/master/globalPlugins/startupOptionWorkaround.py
This script needs to be copied in the scratchpad\globalPlugins directory after having active the scratchpad option (if required).
This script does not fixes the issue but unloads NVDA if it was not configured to start after logon.
Feedback welcomed although it is a “quick dirty script”.
I do not plan to release it as an addon, unless there is a demand.
 
Cheers
 
Cyrille
 
 
 
De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Cyrille via Groups.Io
Envoyé : lundi 19 août 2019 17:56
À : nvda-addons@nvda-addons.groups.io
Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
 
Hello
 
@Jaffar
Reading the ticket, I have understood that :

* The issue occurs only if NVDA is activated on logon screen (seems not to be your case)
* Seems to impact only some computers, not all
@Joseph
Thank you for this information, that you also wrote in the ticket.
Since the fix will not be provided by MS before 2020, I intend to develop this workaround so that my wife does not have to quit NVDA (or forget to do it)
each time she starts her session.
 
Seems that I still just need to figure if current NVDA version was run with the --ease-of-access flag. Is there an internal variable for it ? Or should I
deal with NVDA process command line ?
 
Thanks.
Cheers,
 
Cyrille
 
 

*  
 
De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Jaffar Sidek
Envoyé : lundi 19 août 2019 17:38
À : nvda-addons@nvda-addons.groups.io
Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
 
Hi.  My copy of NVDA running on Windows 10 1903 is not subject to this fault.  It might be that I have Jaws running as the default startup screen reader,
but as of now, NVDA will not start on my desktop unless I explicitly tell it to do so with the usual alt+ctrl+n.  Cheers!
On 8/19/2019 11:22 PM, Joseph Lee wrote:

Hi,

Microsoft is looking into this, and I hope it can be resolved in 20H1 (next year) as 19H2 (the next feature update) is going through testing at
the moment.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via Groups.Io
Sent: Monday, August 19, 2019 8:20 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)
 
Hello all
 
Following the Windows 10 1903 update, NVDA is started after all session startup, regardless wether the corresponding option is checked or not in NVDA
settings.
This problem is described in the following ticket :
On Windows 10 1903 NVDA starts after logon even when this is disabled #9528
This ticket tells us that this issue should be corrected by Microsoft but not so soon, it seems.
 
Has any one of you developed or planned to develop an addon, a simple script or implemented another work-around in NVDA or out of it ?
 
If no, I would plan to make a script or addon to unload NVDA if the option is not checked and if NVDA was run with the –easeofaccess flag. Just not so
sure to have time so soon ; I do not know if this would take me much time or not.
 
Any feedkback, hint or better idea welcome !
 
Cheers,
 
Cyrille
 


Workaround fix - NVDA starts after logon even when this is disabled (Win 10 1903)

Cyrille
 

Hello

 

If NVDA starts after logon even if disabled following Win 10 1903 update, here is a work around script :

https://raw.githubusercontent.com/CyrilleB79/NVDAScripts/master/globalPlugins/startupOptionWorkaround.py

This script needs to be copied in the scratchpad\globalPlugins directory after having active the scratchpad option (if required).

This script does not fixes the issue but unloads NVDA if it was not configured to start after logon.

Feedback welcomed although it is a “quick dirty script”.

I do not plan to release it as an addon, unless there is a demand.

 

Cheers

 

Cyrille

 

 

 

De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Cyrille via Groups.Io
Envoyé : lundi 19 août 2019 17:56
À : nvda-addons@nvda-addons.groups.io
Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)

 

Hello

 

@Jaffar

Reading the ticket, I have understood that :

  • The issue occurs only if NVDA is activated on logon screen (seems not to be your case)
  • Seems to impact only some computers, not all

@Joseph

Thank you for this information, that you also wrote in the ticket.

Since the fix will not be provided by MS before 2020, I intend to develop this workaround so that my wife does not have to quit NVDA (or forget to do it) each time she starts her session.

 

Seems that I still just need to figure if current NVDA version was run with the --ease-of-access flag. Is there an internal variable for it ? Or should I deal with NVDA process command line ?

 

Thanks.

Cheers,

 

Cyrille

 

 

  •  

 

De : nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> De la part de Jaffar Sidek
Envoyé : lundi 19 août 2019 17:38
À : nvda-addons@nvda-addons.groups.io
Objet : Re: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)

 

Hi.  My copy of NVDA running on Windows 10 1903 is not subject to this fault.  It might be that I have Jaws running as the default startup screen reader, but as of now, NVDA will not start on my desktop unless I explicitly tell it to do so with the usual alt+ctrl+n.  Cheers!

On 8/19/2019 11:22 PM, Joseph Lee wrote:

Hi,

Microsoft is looking into this, and I hope it can be resolved in 20H1 (next year) as 19H2 (the next feature update) is going through testing at the moment.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via Groups.Io
Sent: Monday, August 19, 2019 8:20 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] NVDA starts after logon even when this is disabled (Win 10 1903)

 

Hello all

 

Following the Windows 10 1903 update, NVDA is started after all session startup, regardless wether the corresponding option is checked or not in NVDA settings.

This problem is described in the following ticket :

On Windows 10 1903 NVDA starts after logon even when this is disabled #9528

This ticket tells us that this issue should be corrected by Microsoft but not so soon, it seems.

 

Has any one of you developed or planned to develop an addon, a simple script or implemented another work-around in NVDA or out of it ?

 

If no, I would plan to make a script or addon to unload NVDA if the option is not checked and if NVDA was run with the –easeofaccess flag. Just not so sure to have time so soon ; I do not know if this would take me much time or not.

 

Any feedkback, hint or better idea welcome !

 

Cheers,

 

Cyrille

 


Add-on updates before taking a break: Add-on Updater, Enhanced Touch Gestures, Windows 10 App Essentials #addonrelease

 

Hi all,

 

Three add-on updates are available:

 

  • Add-on Updater 19.09: NotepadPlusPlus add-on from Derek Riemer has been registered for add-on updates. Also, a timeout issue seen when trying to download updates after five minutes of inactivity has been resolved. Note that this add-on requires NVDA 2019.2 from now on.
  • Enhanced Touch Gestures 19.09: in addition to Python 3 compatibility, you can now disable touch support completely from everywhere. Previously you were able to do this if a profile other than normal profile was active. In case you do disable touch support completely, NVDA will play a beep when it starts.
  • Windows 10 App Essentials 19.09: app name and version for various universal apps (including Notepad in 20H1 Preview build 18963 and later) will be fetched via a Windows API function introduced in Windows 8. Also, this add-on brings “always on” mode support for future Calculator releases, and effective with this version, address omnibar in classic Edge is no longer treated as a search field (no more search suggestion sounds).

 

You can visit community add-ons website to download these releases. Alternatively, you can use Add-on Updater to check for updates.

 

And with that, I’m out.

Cheers,

Joseph


Re: Outlook extended V1.3 release

 

Hi,

Coming right up from add-on files side – in the middle of releasing my own, so I’ll do so in just a moment.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via Groups.Io
Sent: Tuesday, August 20, 2019 7:29 AM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Outlook extended V1.3 release

 

Hello

The Outlook Extended addon V1.3 is now declared as stable.

@Admins:

Could you update the download link of the website for stable and dev with the following link :

@Noelia:

When you come back from holiday, Could you give me the rights to push my github stable branch to bitbucket repo to update translations ?

My Bitbucket info :

username : CyrilleB79

Thanks.

Cheers,

Cyrille


Outlook extended V1.3 release

Cyrille
 

Hello
The Outlook Extended addon V1.3 is now declared as stable.
@Admins:
Could you update the download link of the website for stable and dev with the following link :
https://github.com/CyrilleB79/outlookExtended/releases/download/V1.3/outlookExtended-1.3.nvda-addon
@Noelia:
When you come back from holiday, Could you give me the rights to push my github stable branch to bitbucket repo to update translations ?
My Bitbucket info :
username : CyrilleB79
e-mail : cyrille.bougot2@...
Thanks.
Cheers,
Cyrille


Welcome to the NVDA Community Add-ons website - Notepad++ #feed

nvda-addons@nvda-addons.groups.io Integration <nvda-addons@...>
 

Notepad++

This addon improves the accessibility of the notepad++ text editor. To learn more, and to read the documentation before installation, visit the addons github page


Notepad++ add-on: now declared stable

 

Hi all,

 

Notepad++ add-on by Derek Riemer is hereby declared stable. This means it’ll be posted under “stable” section of the community add-ons website and will be eligible for update checks via Add-on Updater.

Cheers,

Joseph


Re: Taking a (real) break (at last) # AdminNotice

Noelia Ruiz
 

Since you have mentioned me, I am on holliday too this week. I go back to home on Friday, it will be a long day travelling :) I can take charge of some add-ons which need review or updates in addonFiles, hoping that other reviewers take action too, of course. 
I will not take care about updating the Ython compatibility announcements on the website. Maybe other person wants to do it. I think that all we have to be aware of the fact that all add-ons need to be checked by authors to be compatible with Nvda 2019.-3, and that, with the current system used by NVDA, at least in some releases of NVDA this can happen. This is a part of add-ons maintainance, and we have about two or three months to do this. So, if some add-ons are not updated for NVDA 2019.-3 rc1 is out, we should move them to the dev rersion of the website. But I think we shouldnt be worried.. Authors have time and, if they dont take care without a justification, then people will know about this, if they dont announce them, and people probably dont use their addons. But there is a lot of them. I think we dont need to be worried: good authors are responsible and will take care about add-ons and, if they cannot do it, they should announce so that other maintainers can take charge.


Enviado desde mi iPhone

El 20 ago 2019, a las 4:11, Joseph Lee <joseph.lee22590@...> escribió:

Dear NVDA add-ons community,

 

As much as Python 3 transition work and coordinating add-ons for compatibility has been exciting, it has been a stressful journey also; in fact, this work has worn me out. Coupled with some important life events coming up (hunting for grad schools, for instance), I’m in need of a break, and this time, I’m taking a real break until later this year.

 

As of now more than half of stable add-ons hosted on our community add-ons website are ready for NVDA 2019.3 and Python 3, and others are being planned or are work in progress. Still others need work, and for others not listed on community add-ons website, their fate is unknown at this point. I’m very concerned about speech synthesizers and some popular add-ons the community relies on (namely NVDA Remote and others), some of which are not ready for Python 3 yet and is going to come back to haunt everyone if not addressed soon (and adding to my worries).

 

Therefore I’m stepping away from all NVDA-related action for a while – this includes add-on development apart from one or two upcoming add-on releases in early September. I hope to spring back into action around the time NVDA 2019.3 RC goes online. All that I ask of you is to prove to the world that the add-ons community is strong, resilient, united, and can pull through – making more add-ons Python 3 ready and making sure users of add-ons are not forgotten.

 

Also, I’m handing the administration of this mailing list over to our fellow leaders – Derek Riemer, James Scholes, Noelia Martinez and others – who are more than qualified to lead not only this forum, but the community at this important time. I’ll resume my admin duties once I spring back into action.

 

Thank you.

Cheers,

Joseph


Re: Taking a (real) break (at last) # AdminNotice

Brian's Mail list account
 

Mick seems to be pretty successful at keeping clear to recharge, but I have seen the odd plea for him to look at this and that, and it can be extremely tempting.
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: "Pawel Urbanski" <pawel@e-urbanski.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Tuesday, August 20, 2019 7:47 AM
Subject: Re: [nvda-addons] Taking a (real) break (at last) # AdminNotice


Dear Joseph,
Enjoy your well-deserved break...

On 20/08/2019, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Dear NVDA add-ons community,



As much as Python 3 transition work and coordinating add-ons for
compatibility has been exciting, it has been a stressful journey also; in
fact, this work has worn me out. Coupled with some important life events
coming up (hunting for grad schools, for instance), I'm in need of a break,
and this time, I'm taking a real break until later this year.



As of now more than half of stable add-ons hosted on our community add-ons
website are ready for NVDA 2019.3 and Python 3, and others are being
planned
or are work in progress. Still others need work, and for others not listed
on community add-ons website, their fate is unknown at this point. I'm very
concerned about speech synthesizers and some popular add-ons the community
relies on (namely NVDA Remote and others), some of which are not ready for
Python 3 yet and is going to come back to haunt everyone if not addressed
soon (and adding to my worries).



Therefore I'm stepping away from all NVDA-related action for a while - this
includes add-on development apart from one or two upcoming add-on releases
in early September. I hope to spring back into action around the time NVDA
2019.3 RC goes online. All that I ask of you is to prove to the world that
the add-ons community is strong, resilient, united, and can pull through -
making more add-ons Python 3 ready and making sure users of add-ons are not
forgotten.



Also, I'm handing the administration of this mailing list over to our
fellow
leaders - Derek Riemer, James Scholes, Noelia Martinez and others - who are
more than qualified to lead not only this forum, but the community at this
important time. I'll resume my admin duties once I spring back into action.



Thank you.

Cheers,

Joseph




5661 - 5680 of 14888