Date   

Re: Instructions to manage add-ons documentation on the website

Noelia Ruiz
 

Hello:

@Cyrille: following your instructions, messages seem to be splitted as
expected in .po files.

@Neils: I have modified the message mentioned by you as follows:
To add or update the webpage for your add-on:
• Request an invitation on the translations mailing list. You need to
do this even if the add-on doesn't need translations at this point in
time. A link is provided to the translations mailing list:

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

Cheers

2022-06-14 0:44 GMT+02:00, Cyrille via groups.io
<cyrille.bougot2@...>:

Hi Noelia

Thanks for your fixes.
You have modified the link [4] but that was not my request. Actually I do
not even know if it was correctly rendered on the translated page, since I
have sent my message looking at the .po file, not the resulting page.

My remark was instead the following:

Actual result:
The following text is a single message in the .po file:
* Follow [instructions to download the repo][4]. You may checkout just
the website adding "/website" to the URL to manage add-on
documentation.
* Under the addons subfolder, add an addonRepoName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website. The following examples maybe useful:
-> Thus, there is two list items in the same message and the "*" (star
characters) are included in the message to translate.

Expected result:
The .po should be generated such as bullets do not appear as "*" (star) in
the .po file and such as each list item is a separate message.

How to fix it?
Probably paying attention to indentation when a list item is split on
various lines.

Cheers,

Cyrille

On Mon, Jun 13, 2022 at 12:02 PM, Noelia Ruiz wrote:


Hi Cyrille:

- I haven't modified the first point about submitting pullrequests
since this was not writen by me. This is a work by other person.
- I have reflected, about reference style for links, that this should
be used if URLs aren't too long.
- I've used inline style for link 4 and now it seems to work:

https://addons.nvda-project.org/requirements.fr.html

Let me know if I should fix anything else.

Cheers

2022-06-13 17:02 GMT+02:00, Cyrille via groups.io
<cyrille.bougot2@...>:

Hi Noelia

Thanks for this update of the documentation.
I am translating this documentation.and have seen the following points:

1. You write:
Anyone can submit a pull requeth with requests from authors preferred.
My answer:
For clarity and good spelling, I would write:
Anyone can submit a pull request, but a pull request coming from the
authors
is preferred.

2. The paragraph starting with "Follow [instructions to download the
repo"

and the next bullet are not split in the generated .po file.
Probably the text below the bullet but belonging to the same item should
be
vertically indented of 2 spaces so that it starts at the same level as
the

text following the bullet. Try it to confirm because I am not 100% sure.

3. You write:
"Use "reference" style for links, "
My answer:
Yes, it's better for readability and I usually use it. But for long
links,

ref links do not work, cf. this thread (
https://nvda-addons.groups.io/g/nvda-addons/topic/83889015#15895 ).

Thanks again.

Cheers,

Cyrille

On Sun, Jun 12, 2022 at 11:28 AM, Noelia Ruiz wrote:



Hello: Ive updated the instruction with access8Math, since it contains
dev and stable tags and nested list, AudioThemes (for an example of
tag dev) and teamViewer.mdwn for legacy.
Cheers

2022-06-10 15:01 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977@...>:


I'll mention some examples for tags, like textInformation for an
add-on in the dev section, teamViewer for legacy and other add-on for
dev stable.
For markdown format, I'll copy/sumarize replies of this thread:

https://nvda-addons.groups.io/g/nvda-addons/topic/86095874

2022-06-10 9:22 GMT+02:00, José Manuel Delicado Alcolea via groups.io
<jm.delicado@...>:


Hi,

Also, could you please mention the Markdown limitations and rules in
SRT
and how they impact on translatable strings?

Regards.


El 10/06/2022 a las 8:53, Sukil Etxenike via groups.io escribió:


Hi,

El 10/06/2022 a las 8:49, Noelia Ruiz escribió:


* Under the addons subfolder, add an addonName.mdwn file. Ensure
that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website.

I would link to or provide examples of this point.

Thanks,

Sukil





--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA < https://certification.nvaccess.org >

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es < https://nvda.es >
- @nvda_es < https://twitter.com/nvda_es >

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a
dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***



















Re: Instructions to manage add-ons documentation on the website

neils
 

Noelia,

Definitely an improvement and very helpful to have examples to copy. I have two suggestions:
1. A point that confused me is requesting to join the translation team when translations weren't appropriate yet. I think adding the sentence "You need to do this even if the add-on doesn't need translations at this point in time".
2. The second suggestion is that for those that are new, requesting an invitation to join the translation team needs to add the link to join. My guess is that the link is https://groups.io/g/nvda-translations and then posting a request, but since I haven't done this, maybe that's not how to request joining (which is all the more reason why this needs a bit more info).

Thanks again for taking this on. I'm sure it will help other newbies write add-ons.

    Neil


On Mon, Jun 13, 2022 at 3:44 PM Cyrille via groups.io <cyrille.bougot2=laposte.net@groups.io> wrote:
Hi Noelia

Thanks for your fixes.
You have modified the link [4] but that was not my request. Actually I do not even know if it was correctly rendered on the translated page, since I have sent my message looking at the .po file, not the resulting page.

My remark was instead the following:

Actual result:
The following text is a single message in the .po file:
* Follow [instructions to download the repo][4]. You may checkout just
the website adding "/website" to the URL to manage add-on
documentation.
* Under the addons subfolder, add an addonRepoName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website. The following examples maybe useful:
-> Thus, there is two list items in the same message and the "*" (star characters) are included in the message to translate.

Expected result:
The .po should be generated such as bullets do not appear as "*" (star) in the .po file and such as each list item is a separate message.

How to fix it?
Probably paying attention to indentation when a list item is split on various lines.

Cheers,

Cyrille



On Mon, Jun 13, 2022 at 12:02 PM, Noelia Ruiz wrote:
Hi Cyrille:

- I haven't modified the first point about submitting pullrequests
since this was not writen by me. This is a work by other person.
- I have reflected, about reference style for links, that this should
be used if URLs aren't too long.
- I've used inline style for link 4 and now it seems to work:

https://addons.nvda-project.org/requirements.fr.html

Let me know if I should fix anything else.

Cheers

2022-06-13 17:02 GMT+02:00, Cyrille via groups.io
<cyrille.bougot2=laposte.net@groups.io>:
Hi Noelia

Thanks for this update of the documentation.
I am translating this documentation.and have seen the following points:

1. You write:
Anyone can submit a pull requeth with requests from authors preferred.
My answer:
For clarity and good spelling, I would write:
Anyone can submit a pull request, but a pull request coming from the authors
is preferred.

2. The paragraph starting with "Follow [instructions to download the repo"
and the next bullet are not split in the generated .po file.
Probably the text below the bullet but belonging to the same item should be
vertically indented of 2 spaces so that it starts at the same level as the
text following the bullet. Try it to confirm because I am not 100% sure.

3. You write:
"Use "reference" style for links, "
My answer:
Yes, it's better for readability and I usually use it. But for long links,
ref links do not work, cf. this thread (
https://nvda-addons.groups.io/g/nvda-addons/topic/83889015#15895 ).

Thanks again.

Cheers,

Cyrille

On Sun, Jun 12, 2022 at 11:28 AM, Noelia Ruiz wrote:


Hello: Ive updated the instruction with access8Math, since it contains
dev and stable tags and nested list, AudioThemes (for an example of
tag dev) and teamViewer.mdwn for legacy.
Cheers

2022-06-10 15:01 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977=gmail.com@groups.io>:

I'll mention some examples for tags, like textInformation for an
add-on in the dev section, teamViewer for legacy and other add-on for
dev stable.
For markdown format, I'll copy/sumarize replies of this thread:

https://nvda-addons.groups.io/g/nvda-addons/topic/86095874

2022-06-10 9:22 GMT+02:00, José Manuel Delicado Alcolea via groups.io
<jm.delicado=nvda.es@groups.io>:

Hi,

Also, could you please mention the Markdown limitations and rules in
SRT
and how they impact on translatable strings?

Regards.


El 10/06/2022 a las 8:53, Sukil Etxenike via groups.io escribió:

Hi,

El 10/06/2022 a las 8:49, Noelia Ruiz escribió:

* Under the addons subfolder, add an addonName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website.

I would link to or provide examples of this point.

Thanks,

Sukil





--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA < https://certification.nvaccess.org >

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es < https://nvda.es >
- @nvda_es < https://twitter.com/nvda_es >

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a
dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***















Re: Instructions to manage add-ons documentation on the website

Cyrille
 

Hi Noelia

Thanks for your fixes.
You have modified the link [4] but that was not my request. Actually I do not even know if it was correctly rendered on the translated page, since I have sent my message looking at the .po file, not the resulting page.

My remark was instead the following:

Actual result:
The following text is a single message in the .po file:
* Follow [instructions to download the repo][4]. You may checkout just
the website adding "/website" to the URL to manage add-on
documentation.
* Under the addons subfolder, add an addonRepoName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website. The following examples maybe useful:
-> Thus, there is two list items in the same message and the "*" (star characters) are included in the message to translate.

Expected result:
The .po should be generated such as bullets do not appear as "*" (star) in the .po file and such as each list item is a separate message.

How to fix it?
Probably paying attention to indentation when a list item is split on various lines.

Cheers,

Cyrille



On Mon, Jun 13, 2022 at 12:02 PM, Noelia Ruiz wrote:
Hi Cyrille:

- I haven't modified the first point about submitting pullrequests
since this was not writen by me. This is a work by other person.
- I have reflected, about reference style for links, that this should
be used if URLs aren't too long.
- I've used inline style for link 4 and now it seems to work:

https://addons.nvda-project.org/requirements.fr.html

Let me know if I should fix anything else.

Cheers

2022-06-13 17:02 GMT+02:00, Cyrille via groups.io
<cyrille.bougot2@...>:
Hi Noelia

Thanks for this update of the documentation.
I am translating this documentation.and have seen the following points:

1. You write:
Anyone can submit a pull requeth with requests from authors preferred.
My answer:
For clarity and good spelling, I would write:
Anyone can submit a pull request, but a pull request coming from the authors
is preferred.

2. The paragraph starting with "Follow [instructions to download the repo"
and the next bullet are not split in the generated .po file.
Probably the text below the bullet but belonging to the same item should be
vertically indented of 2 spaces so that it starts at the same level as the
text following the bullet. Try it to confirm because I am not 100% sure.

3. You write:
"Use "reference" style for links, "
My answer:
Yes, it's better for readability and I usually use it. But for long links,
ref links do not work, cf. this thread (
https://nvda-addons.groups.io/g/nvda-addons/topic/83889015#15895 ).

Thanks again.

Cheers,

Cyrille

On Sun, Jun 12, 2022 at 11:28 AM, Noelia Ruiz wrote:


Hello: Ive updated the instruction with access8Math, since it contains
dev and stable tags and nested list, AudioThemes (for an example of
tag dev) and teamViewer.mdwn for legacy.
Cheers

2022-06-10 15:01 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977@...>:

I'll mention some examples for tags, like textInformation for an
add-on in the dev section, teamViewer for legacy and other add-on for
dev stable.
For markdown format, I'll copy/sumarize replies of this thread:

https://nvda-addons.groups.io/g/nvda-addons/topic/86095874

2022-06-10 9:22 GMT+02:00, José Manuel Delicado Alcolea via groups.io
<jm.delicado@...>:

Hi,

Also, could you please mention the Markdown limitations and rules in
SRT
and how they impact on translatable strings?

Regards.


El 10/06/2022 a las 8:53, Sukil Etxenike via groups.io escribió:

Hi,

El 10/06/2022 a las 8:49, Noelia Ruiz escribió:

* Under the addons subfolder, add an addonName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website.

I would link to or provide examples of this point.

Thanks,

Sukil





--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA < https://certification.nvaccess.org >

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es < https://nvda.es >
- @nvda_es < https://twitter.com/nvda_es >

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a
dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***















Re: How to avoid garbage handler error like this?

Cyrille
 

Hi Alberto

Sorry, I have no idea of advice for you.
The main idea is to avoid to have reference cycles.
Let's hope that someone else can comment here.

Cheers,

Cyrille
*




On Mon, Jun 13, 2022 at 07:14 AM, Alberto Buffolino wrote:
Cyrille via groups.io, il 13/6/2022, ha scritto:
On your side, did you follow these indications?
Alberto:
Hi Cyrille,
thanks, I had never hear of that page.
I'm quite sure that warnings are caused by the following method:
***
# to get NVDA script gestures, regardless its user remap
def getScriptGestures(scriptFunc):
from inputCore import manager
allGestures = manager.getAllGestureMappings()
scriptGestures = []
try:
scriptCategory = scriptFunc.category if hasattr(scriptFunc,
"category") else scriptFunc.__self__.__class__.scriptCategory
scriptDoc = scriptFunc.__doc__
script = allGestures[scriptCategory][scriptDoc]
scriptGestures = script.gestures
except:
pass
return scriptGestures
***
because, obviously, it collects a lot of stuff according to current
object during gesture bindings.
Maybe I must modify the caller code, changing from:
for gesture in
getScriptGestures(commands.script_reportCurrentSelection): ...
to:
scriptGestures = getScriptGestures(commands.script_reportCurrentSelection)
for gesture in scriptGestures: ...
Does it make sense, in your opinion?
Alberto


Re: Instructions to manage add-ons documentation on the website

Noelia Ruiz
 

Hi Cyrille:

- I haven't modified the first point about submitting pullrequests
since this was not writen by me. This is a work by other person.
- I have reflected, about reference style for links, that this should
be used if URLs aren't too long.
- I've used inline style for link 4 and now it seems to work:

https://addons.nvda-project.org/requirements.fr.html

Let me know if I should fix anything else.

Cheers

2022-06-13 17:02 GMT+02:00, Cyrille via groups.io
<cyrille.bougot2@...>:

Hi Noelia

Thanks for this update of the documentation.
I am translating this documentation.and have seen the following points:

1. You write:
Anyone can submit a pull requeth with requests from authors preferred.
My answer:
For clarity and good spelling, I would write:
Anyone can submit a pull request, but a pull request coming from the authors
is preferred.

2. The paragraph starting with "Follow [instructions to download the repo"
and the next bullet are not split in the generated .po file.
Probably the text below the bullet but belonging to the same item should be
vertically indented of 2 spaces so that it starts at the same level as the
text following the bullet. Try it to confirm because I am not 100% sure.

3. You write:
"Use "reference" style for links, "
My answer:
Yes, it's better for readability and I usually use it. But for long links,
ref links do not work, cf. this thread (
https://nvda-addons.groups.io/g/nvda-addons/topic/83889015#15895 ).

Thanks again.

Cheers,

Cyrille

On Sun, Jun 12, 2022 at 11:28 AM, Noelia Ruiz wrote:


Hello: Ive updated the instruction with access8Math, since it contains
dev and stable tags and nested list, AudioThemes (for an example of
tag dev) and teamViewer.mdwn for legacy.
Cheers

2022-06-10 15:01 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977@...>:

I'll mention some examples for tags, like textInformation for an
add-on in the dev section, teamViewer for legacy and other add-on for
dev stable.
For markdown format, I'll copy/sumarize replies of this thread:

https://nvda-addons.groups.io/g/nvda-addons/topic/86095874

2022-06-10 9:22 GMT+02:00, José Manuel Delicado Alcolea via groups.io
<jm.delicado@...>:

Hi,

Also, could you please mention the Markdown limitations and rules in
SRT
and how they impact on translatable strings?

Regards.


El 10/06/2022 a las 8:53, Sukil Etxenike via groups.io escribió:

Hi,

El 10/06/2022 a las 8:49, Noelia Ruiz escribió:

* Under the addons subfolder, add an addonName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website.

I would link to or provide examples of this point.

Thanks,

Sukil





--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA < https://certification.nvaccess.org >

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es < https://nvda.es >
- @nvda_es < https://twitter.com/nvda_es >

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a
dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***















Re: Instructions to manage add-ons documentation on the website

Cyrille
 

Hi Noelia

Thanks for this update of the documentation.
I am translating this documentation.and have seen the following points:

1. You write:
Anyone can submit a pull requeth with requests from authors preferred.
My answer:
For clarity and good spelling, I would write:
Anyone can submit a pull request, but a pull request coming from the authors is preferred.

2. The paragraph starting with "Follow [instructions to download the repo" and the next bullet are not split in the generated .po file.
Probably the text below the bullet but belonging to the same item should be vertically indented of 2 spaces so that it starts at the same level as the text following the bullet. Try it to confirm because I am not 100% sure.

3. You write:
"Use "reference" style for links, "
My answer:
Yes, it's better for readability and I usually use it. But for long links, ref links do not work, cf. this thread.

Thanks again.

Cheers,

Cyrille


On Sun, Jun 12, 2022 at 11:28 AM, Noelia Ruiz wrote:
Hello: Ive updated the instruction with access8Math, since it contains
dev and stable tags and nested list, AudioThemes (for an example of
tag dev) and teamViewer.mdwn for legacy.
Cheers

2022-06-10 15:01 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977@...>:
I'll mention some examples for tags, like textInformation for an
add-on in the dev section, teamViewer for legacy and other add-on for
dev stable.
For markdown format, I'll copy/sumarize replies of this thread:

https://nvda-addons.groups.io/g/nvda-addons/topic/86095874

2022-06-10 9:22 GMT+02:00, José Manuel Delicado Alcolea via groups.io
<jm.delicado@...>:
Hi,

Also, could you please mention the Markdown limitations and rules in SRT
and how they impact on translatable strings?

Regards.


El 10/06/2022 a las 8:53, Sukil Etxenike via groups.io escribió:
Hi,

El 10/06/2022 a las 8:49, Noelia Ruiz escribió:
* Under the addons subfolder, add an addonName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website.

I would link to or provide examples of this point.

Thanks,

Sukil





--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA <https://certification.nvaccess.org>

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es <https://nvda.es>
- @nvda_es <https://twitter.com/nvda_es>

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***











Re: How to avoid garbage handler error like this?

Alberto Buffolino
 

Cyrille via groups.io, il 13/6/2022, ha scritto:
On your side, did you follow these indications?
Alberto:
Hi Cyrille,
thanks, I had never hear of that page.
I'm quite sure that warnings are caused by the following method:
***
# to get NVDA script gestures, regardless its user remap
def getScriptGestures(scriptFunc):
from inputCore import manager
allGestures = manager.getAllGestureMappings()
scriptGestures = []
try:
scriptCategory = scriptFunc.category if hasattr(scriptFunc, "category") else scriptFunc.__self__.__class__.scriptCategory
scriptDoc = scriptFunc.__doc__
script = allGestures[scriptCategory][scriptDoc]
scriptGestures = script.gestures
except:
pass
return scriptGestures
***
because, obviously, it collects a lot of stuff according to current object during gesture bindings.
Maybe I must modify the caller code, changing from:
for gesture in getScriptGestures(commands.script_reportCurrentSelection): ...
to:
scriptGestures = getScriptGestures(commands.script_reportCurrentSelection)
for gesture in scriptGestures: ...
Does it make sense, in your opinion?
Alberto


Re: How to avoid garbage handler error like this?

Cyrille
 

Hello Alberto

I am interested if you get valuable information about this issue or a practical feedback if you succeed in solving it.

I  occasionally get such garbage errors when using alt+Number scripts in my Outlook Extended add-on. And I can also reproduce 100% of the times a garbage error with only one warning when using a test mode of Outlook Extended.
I have tried to follow NVAccess' indications to debug such issues, but without success for now.

On your side, did you follow these indications?

Cheers,

Cyrille


How to avoid garbage handler error like this?

Alberto Buffolino
 

Hi all,
an user reported me the log fragment I paste below, relative to ColumnsReview and garbage handler.
The reported lines regars the collecting of all NVDA gestures (via inputCore.manager.getAllGestureMappings), for some gesture → script mapping made by the add-on.
All works, but garbageHandler occasionally raises these warnings, that should indicate a undesiderable memory status, if I understand well.
So, how I can avoid/solve this situation optimizing my code?
***
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.178) - MainThread (800):
Garbage collector has found one or more unreachable objects. See further warnings for specific objects.
Stack trace:
  File "nvda.pyw", line 390, in <module>
  File "core.pyc", line 776, in main
  File "wx\core.pyc", line 2237, in MainLoop
  File "gui\__init__.pyc", line 762, in Notify
  File "core.pyc", line 738, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "eventHandler.pyc", line 68, in _queueEventCallback
  File "eventHandler.pyc", line 280, in executeEvent
  File "eventHandler.pyc", line 293, in doPreGainFocus
  File "api.pyc", line 169, in setFocusObject
  File "baseObject.pyc", line 42, in __get__
  File "baseObject.pyc", line 146, in _getPropertyViaCache
  File "NVDAObjects\__init__.pyc", line 582, in _get_container
  File "baseObject.pyc", line 42, in __get__
  File "baseObject.pyc", line 146, in _getPropertyViaCache
  File "NVDAObjects\IAccessible\__init__.pyc", line 1029, in _get_parent
  File "NVDAObjects\__init__.pyc", line 142, in __call__
  File "C:\Users\cagri\AppData\Roaming\nvda\addons\columnsReview\globalPlugins\columnsReview\__init__.py", line 282, in initOverlayClass
    self.bindCRGestures()
  File "C:\Users\cagri\AppData\Roaming\nvda\addons\columnsReview\globalPlugins\columnsReview\__init__.py", line 249, in bindCRGestures
    for gesture in getScriptGestures(commands.script_reportCurrentSelection):
  File "C:\Users\cagri\AppData\Roaming\nvda\addons\columnsReview\globalPlugins\columnsReview\commonFunc.py", line 39, in getScriptGestures
    allGestures = manager.getAllGestureMappings()
  File "inputCore.pyc", line 598, in getAllGestureMappings
  File "inputCore.pyc", line 657, in __init__
  File "inputCore.pyc", line 740, in addObj
  File "inputCore.pyc", line 709, in makeNormalScriptInfo
  File "inputCore.pyc", line 762, in __init__
  File "garbageHandler.pyc", line 28, in __del__
  File "garbageHandler.pyc", line 69, in notifyObjectDeletion
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.178) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExIAccessible object at 0x0A454FF0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.178) - MainThread (800):
Deleting unreachable object <NVDAObjects.IAccessible.chromium.ChromeVBuf object at 0x00AEF490>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.178) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExMailItemRowListItemUIA object at 0x0D2D2C30>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExDesktopWindowNVDAObject object at 0x0D2D2F70>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible) ptr=0xc1c63c0 at b36e40>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExinterfaceIa2WebIAccessible object at 0x007DED90>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_EditableTextExNVDAObjectExinterfaceDocumentIa2WebIAccessible object at 0x0A454E10>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExUIAWindowNVDAObject object at 0x00B30730>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExUIAWindowNVDAObject object at 0x0D2D28B0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExUIAWindowNVDAObject object at 0x0D2D2170>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExIAccessible object at 0x0D2D2710>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.179) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExWindowRootIAccessible object at 0x0D2D2210>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExinterfaceWindowRootIAccessible object at 0x0693F410>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExinterfaceIa2WebIAccessible object at 0x00B30970>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExinterfaceWindowRootIAccessible object at 0x00B56910>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <'chrome' (appName 'chrome', process ID 17204) at address b30c90>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExUIAWindowNVDAObject object at 0x0D2D29D0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExUIAWindowNVDAObject object at 0x0D2D2110>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <POINTER(IUIAutomationElement) ptr=0xc024c10 at a4485d0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.180) - MainThread (800):
Deleting unreachable object <POINTER(IUIAutomationSelectionItemPattern) ptr=0xc322318 at b36800>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.181) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible2) ptr=0xc3451a4 at b36300>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.181) - MainThread (800):
Deleting unreachable object <POINTER(IAccessibleText) ptr=0xc3451ec at b363a0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.181) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible2) ptr=0xc4e3b9c at b36080>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.181) - MainThread (800):
Deleting unreachable object <POINTER(IAccessibleAction) ptr=0xc4e3be4 at 6985440>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.181) - MainThread (800):
Deleting unreachable object <POINTER(IAccessibleText) ptr=0xc4e40f4 at b36b20>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.182) - MainThread (800):
Deleting unreachable object <POINTER(IUIAutomationElement) ptr=0xc261e28 at 84bee0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.183) - MainThread (800):
Deleting unreachable object <POINTER(IUIAutomationElement) ptr=0xc261d08 at 69853a0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.183) - MainThread (800):
Deleting unreachable object <POINTER(IUIAutomationElement) ptr=0xc261fd8 at 69852b0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.183) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible) ptr=0xc1c6310 at b36d00>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.184) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible) ptr=0xc1c64c8 at b369e0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.184) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible) ptr=0xc2133ac at 84be90>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.185) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExinterfaceIa2WebIAccessible object at 0x007DE8B0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.185) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible2) ptr=0xc3451a4 at a448490>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.185) - MainThread (800):
Deleting unreachable object <POINTER(IAccessibleText) ptr=0xc3451ec at 6997da0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.185) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible) ptr=0xc1d625c at b36f30>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.189) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExDesktopWindowNVDAObject object at 0x007DE6D0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.189) - MainThread (800):
Deleting unreachable object <POINTER(IUIAutomationElement) ptr=0xc261ba0 at 6997b20>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.190) - MainThread (800):
Deleting unreachable object <POINTER(IUIAutomationElement) ptr=0xc261ac8 at a448580>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.190) - MainThread (800):
Deleting unreachable object <POINTER(IAccessible2) ptr=0xc3451a4 at da1fb70>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.190) - MainThread (800):
Deleting unreachable object <POINTER(IAccessibleText) ptr=0xc3451ec at 6997ad0>
WARNING - garbageHandler.notifyObjectDeletion (09:14:11.191) - MainThread (800):
Deleting unreachable object <NVDAObjects.Dynamic_ClipboardCommandAnnouncementNVDAObjectExDesktopWindowNVDAObject object at 0x007DEDF0>
ERROR - garbageHandler._collectionCallback (09:14:11.191) - MainThread (800):
Found at least 41 unreachable objects in run
***
Alberto


Re: update channel selector

Brian's Mail list account
 

Hmm, I thought |I had cut and pasted the bits relevant to the issues mentioned but they seem not to have got into my email.
Most peculiar.
Brian

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

----- Original Message -----
From: "Cyrille via groups.io" <cyrille.bougot2@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Sunday, June 12, 2022 11:26 PM
Subject: Re: [nvda-addons] update channel selector


Hi Brian and all

You write:
That was what the reporter intimated on the post in the issues list that I
read yesterday. I suggest you take it up there.

Again, as asked to you, a link would help to confirm or infirm what you write.

Since I seem to be the reporter in question, here are the links:
* NVDA issue: https://github.com/nvaccess/nvda/issues/13786
* Update Channel Selector issue: https://github.com/nvda-es/updateChannel/issues/5

And no, I did not write that "even if its no longer present, it can cause crashes due to entries in the config file of nvda". Please read both tickets since the situation is more complex and the add-on was actually installed in my NVDA profile folder. Thanks.

But the good news is that a fix has been quickly developed (thanks Lukasz) and should be present in the next release of the add-on (thanks José-Manuel)!
Cheers,

Cyrille

On Sun, Jun 12, 2022 at 06:08 AM, Brian's Mail list account wrote:


That was what the reporter intimated on the post in the issues list that I

read yesterday. I suggest you take it up there.
I was merely wondering if anyone on here had seen it. You say its been
moved to a discussion now, well, I was unaware of this as I'm probably not

able to view it.
There was no malicious intent, I can assure you. I find these little
buglets fascinating myself. Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "José Manuel Delicado Alcolea via groups.io"
<jm.delicado@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, June 11, 2022 10:50 AM
Subject: Re: [nvda-addons] update channel selector



Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read
that it causes crashes even when it is not present, but this is
completely false. The problem of portable copies is being discussed on
issue 5 of Update Channel Selector repo, so there is no need to have two
parallel conversations about the same topic, specially when the second
one includes false statements.

Regards.


El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io
escribió:

I noticed on the issues tracker that somebody has pointed out that if
this add on has been used but even if its no longer present, it can
cause crashes due to entries in the config file of nvda when creating
a portable copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to
remove any changes or maybe NVDA itsself should do so, before
creating a portable copy.
Brian
--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA < https://certification.nvaccess.org >

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es < https://nvda.es >
- @nvda_es < https://twitter.com/nvda_es >

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***







--------------------------------------------------------------------------------



Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read
that
it causes crashes even when it is not present, but this is completely
false.
The problem of portable copies is being discussed on issue 5 of Update
Channel Selector repo, so there is no need to have two parallel
conversations about the same topic, specially when the second one includes

false statements.

Regards.




El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io
escribió:

I noticed on the issues tracker that somebody has pointed out that if
this add on has been used but even if its no longer present, it can cause
crashes due to entries in the config file of nvda when creating a portable

copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to remove
any changes or maybe NVDA itsself should do so, before creating a
portable
copy.
Brian


--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo



Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001
- jm.delicado@...
- www.NVDA.es
- @nvda_es

***Este mensaje y sus adjuntos están dirigidos a su destinatario y pueden

contener información exclusiva o confidencial. La utilización, copia o
divulgación de los mismos por parte de alguien diferente a dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***


Re: update channel selector

Cyrille
 

Hi Brian and all

You write:
That was what the reporter intimated on the post in the issues list that I
read yesterday. I suggest you take it up there.

Again, as asked to you, a link would help to confirm or infirm what you write.

Since I seem to be the reporter in question, here are the links:
* NVDA issue: https://github.com/nvaccess/nvda/issues/13786
* Update Channel Selector issue: https://github.com/nvda-es/updateChannel/issues/5

And no, I did not write that "even if its no longer present, it can cause crashes due to entries in the config file of nvda". Please read both tickets since the situation is more complex and the add-on was actually installed in my NVDA profile folder. Thanks.

But the good news is that a fix has been quickly developed (thanks Lukasz) and should be present in the next release of the add-on (thanks José-Manuel)!
Cheers,

Cyrille



On Sun, Jun 12, 2022 at 06:08 AM, Brian's Mail list account wrote:
That was what the reporter intimated on the post in the issues list that I
read yesterday. I suggest you take it up there.
I was merely wondering if anyone on here had seen it. You say its been
moved to a discussion now, well, I was unaware of this as I'm probably not
able to view it.
There was no malicious intent, I can assure you. I find these little
buglets fascinating myself. Brian

--
bglists@...
Sent via blueyonder.(Virgin media)
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "José Manuel Delicado Alcolea via groups.io"
<jm.delicado@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, June 11, 2022 10:50 AM
Subject: Re: [nvda-addons] update channel selector


Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read
that it causes crashes even when it is not present, but this is
completely false. The problem of portable copies is being discussed on
issue 5 of Update Channel Selector repo, so there is no need to have two
parallel conversations about the same topic, specially when the second
one includes false statements.

Regards.


El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io
escribió:
I noticed on the issues tracker that somebody has pointed out that if
this add on has been used but even if its no longer present, it can
cause crashes due to entries in the config file of nvda when creating
a portable copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to
remove any changes or maybe NVDA itsself should do so, before
creating a portable copy.
Brian
--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA <https://certification.nvaccess.org>

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es <https://nvda.es>
- @nvda_es <https://twitter.com/nvda_es>

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***







--------------------------------------------------------------------------------


Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read that
it causes crashes even when it is not present, but this is completely false.
The problem of portable copies is being discussed on issue 5 of Update
Channel Selector repo, so there is no need to have two parallel
conversations about the same topic, specially when the second one includes
false statements.

Regards.




El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io
escribió:

I noticed on the issues tracker that somebody has pointed out that if
this add on has been used but even if its no longer present, it can cause
crashes due to entries in the config file of nvda when creating a portable
copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to remove
any changes or maybe NVDA itsself should do so, before creating a portable
copy.
Brian


--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo



Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001
- jm.delicado@...
- www.NVDA.es
- @nvda_es

***Este mensaje y sus adjuntos están dirigidos a su destinatario y pueden
contener información exclusiva o confidencial. La utilización, copia o
divulgación de los mismos por parte de alguien diferente a dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***


Re: Instructions to manage add-ons documentation on the website

Noelia Ruiz
 

Hello: Ive updated the instruction with access8Math, since it contains
dev and stable tags and nested list, AudioThemes (for an example of
tag dev) and teamViewer.mdwn for legacy.
Cheers

2022-06-10 15:01 GMT+02:00, Noelia Ruiz via groups.io
<nrm1977@...>:

I'll mention some examples for tags, like textInformation for an
add-on in the dev section, teamViewer for legacy and other add-on for
dev stable.
For markdown format, I'll copy/sumarize replies of this thread:

https://nvda-addons.groups.io/g/nvda-addons/topic/86095874

2022-06-10 9:22 GMT+02:00, José Manuel Delicado Alcolea via groups.io
<jm.delicado@...>:
Hi,

Also, could you please mention the Markdown limitations and rules in SRT
and how they impact on translatable strings?

Regards.


El 10/06/2022 a las 8:53, Sukil Etxenike via groups.io escribió:
Hi,

El 10/06/2022 a las 8:49, Noelia Ruiz escribió:
* Under the addons subfolder, add an addonName.mdwn file. Ensure that
it contains a title and tags such as dev, stable or legacy, so that
the webpage can be rendered in the corresponding sections of the
website.

I would link to or provide examples of this point.

Thanks,

Sukil





--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA <https://certification.nvaccess.org>

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es <https://nvda.es>
- @nvda_es <https://twitter.com/nvda_es>

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***











Re: update channel selector

Brian's Mail list account
 

That was what the reporter intimated on the post in the issues list that I read yesterday. I suggest you take it up there.
I was merely wondering if anyone on here had seen it. You say its been moved to a discussion now, well, I was unaware of this as I'm probably not able to view it.
There was no malicious intent, I can assure you. I find these little buglets fascinating myself. Brian

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

----- Original Message -----
From: "José Manuel Delicado Alcolea via groups.io" <jm.delicado@...>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Saturday, June 11, 2022 10:50 AM
Subject: Re: [nvda-addons] update channel selector


Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read
that it causes crashes even when it is not present, but this is
completely false. The problem of portable copies is being discussed on
issue 5 of Update Channel Selector repo, so there is no need to have two
parallel conversations about the same topic, specially when the second
one includes false statements.

Regards.


El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io escribió:
I noticed on the issues tracker that somebody has pointed out that if
this add on has been used but even if its no longer present, it can
cause crashes due to entries in the config file of nvda when creating
a portable copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to
remove any changes or maybe NVDA itsself should do so, before
creating a portable copy.
Brian
--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
Experto certificado en NVDA <https://certification.nvaccess.org>

Logotipo de la comunidad hispanohablante de NVDA
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001 <tel:+34910053325,2001>
- jm.delicado@...
- www.NVDA.es <https://nvda.es>
- @nvda_es <https://twitter.com/nvda_es>

***Este mensaje y sus adjuntos están dirigidos a su destinatario y
pueden contener información exclusiva o confidencial. La utilización,
copia o divulgación de los mismos por parte de alguien diferente a dicho
destinatario no está permitida sin autorización. Si ha recibido este
mensaje por error, le rogamos que lo comunique por esta misma vía y
seguidamente lo destruya.***






--------------------------------------------------------------------------------


Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read that it causes crashes even when it is not present, but this is completely false. The problem of portable copies is being discussed on issue 5 of Update Channel Selector repo, so there is no need to have two parallel conversations about the same topic, specially when the second one includes false statements.

Regards.




El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io escribió:

I noticed on the issues tracker that somebody has pointed out that if this add on has been used but even if its no longer present, it can cause crashes due to entries in the config file of nvda when creating a portable copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to remove any changes or maybe NVDA itsself should do so, before creating a portable copy.
Brian


--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo



Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001
- jm.delicado@...
- www.NVDA.es
- @nvda_es

***Este mensaje y sus adjuntos están dirigidos a su destinatario y pueden contener información exclusiva o confidencial. La utilización, copia o divulgación de los mismos por parte de alguien diferente a dicho destinatario no está permitida sin autorización. Si ha recibido este mensaje por error, le rogamos que lo comunique por esta misma vía y seguidamente lo destruya.***


Re: Telegram group for discussing NVDA addons development topics

Sarah k Alawami
 

Uh, I'm using telegram accessibly on windows. But that can be discussed on the chat group. I've joined the group btw.

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of René Linke
Sent: Friday, June 10, 2022 9:59 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Telegram group for discussing NVDA addons development topics

Hi,

NVDA is only for Windows, such as Desktops, Laptops, and Tablets with a Microsoft Windows operating system. IMHO it doesn't make sense to add a new group on other platforms, that isn't designed for NVDA.
That would just split the community. And keep out all others they don't have an account there or cannot make one.
And by the way, Telegram is not useable in all coutnries around the world.

Cheers.
René


Re: About Tesseract OCR.

Javi Domínguez
 

Hello.


You have a pull request that fixes both issues.


https://github.com/ruifontes/tesseractOCR/pull/2


Greetings


Javi Dominguez

El 05/06/2022 a las 23:01, Javi Domínguez via groups.io escribió:
Hello again.

I have run wia-cmd-scanner.exe directly from the command line, in the Windows CMD, and it has worked perfectly.

However from the addon it doesn't work. stderr shows:

b'The system cannot find the specified path.\r\n'

I hope this helps. It's late and I can't do any more research. Tomorrow dawns very early.

Good nitht

Javi

El 05/06/2022 a las 22:24, Javi Domínguez via groups.io escribió:
Hello.


* It is a limitation of the routine to get the complete path of the file...

If you can help bettering the routine, I will be glad!

OK. I'll take a look at that.


* The scanner is recognized as WIA compatible?

what do you mean with "is recognized as WIA compatible"? Yes, the scanner is WIA compliant, other apps recognize it but the addon I don't know, it just doesn't do anything.


* What Windows version?
Windows 10 21H2 (x64) build 19044.1706


* So, I should name each thread differently...

Yes, it would be convenient.


* And, before starting another thread, verify if it is active, right?

I think so. I would wait for the current thread to finish before starting another.


Note that if you assign the new thread to self._thread, the old thread will continue to run until it finishes but you will no longer have a reference to it. You will only be able to access it via threading.enumerate().


You may need a method to kill threads that are stuck or taking too long.


Greetings


Javi


El 05/06/2022 a las 20:34, Rui Fontes escribió:
Hola Javi!


Comments in midle of your message marked with *...


Às 18:47 de 05/06/2022, Javi Domínguez escreveu:
When I try to recognize a file on the desktop two things happen:

1. If this is the first time a file is recognized, it says "file not supported" (tested with PDF and BMP file types). The same file recognized from a folder in Windows explorer works fine.

* It is a limitation of the routine to get the complete path of the file...

If you can help bettering the routine, I will be glad!



2. If another file has been recognized before, it process any file even if it is not of a supported type. In any case, supported type or not, it always shows the result of the previous recognition, not the requested file. Even after manually deleting the oc.txt and ocr-xxx.png files from the addon's images folder, it re-processes the previously requested file.

* It was an error on code... The path of last document was not cleared, so list of ocr-xxx.png file was created again...



On the other hand, recognition from scanner does not work for me. My scanner is HP Scanjet G2410, It may not be supported but the addon does not speak any message about it. The thread that processes this remains active and never terminates. If the script is executed again, another thread is launched that also remains active and so on forever. It is normal for the user, if he does not receive a response, to try to run it again, so you can end up with a lot of active threads.
* The scanner is recognized as WIA compatible?

* What Windows version?


I have the habit of naming the treads that I use to be able to debug better with threading.enumerate(). I have added the line to __init__.py
self._thread.name = "tesseractOCR"
before starting the thread to do these tests.
* So, I should name each thread differently...

* And, before starting another thread, verify if it is active, right?


finally, in terms of user experience, I think you need to give more information about what is happening. Sometimes, if the recognition takes time, the user does not know if it is working correctly or not.
* It is schedulled for next version...


Thanks!


Rui Fontes












Re: update channel selector

Noelia Ruiz
 

Hello: Here we can open topics even if they are being discussed in other places. Anyway, please don"t spread statements about add-ons if you aren"t sure that they are true, and try to provide links to verify sources. Thanks
Enviado desde mi iPhone

El 11 jun 2022, a las 11:50, José Manuel Delicado Alcolea via groups.io <jm.delicado@...> escribió:



Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read that it causes crashes even when it is not present, but this is completely false. The problem of portable copies is being discussed on issue 5 of Update Channel Selector repo, so there is no need to have two parallel conversations about the same topic, specially when the second one includes false statements.

Regards.


El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io escribió:
I noticed on the issues tracker that somebody  has pointed out that if this add on has been used but even if its no longer present, it can cause crashes due to entries in the config file of nvda when creating a portable copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to remove any changes  or maybe NVDA itsself should do so, before creating a portable copy.
Brian

--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo
NVDA_certified_expert.png

firma_correo_nvdaes.png
Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001
- jm.delicado@...
- www.NVDA.es
- @nvda_es

***Este mensaje y sus adjuntos están dirigidos a su destinatario y pueden contener información exclusiva o confidencial. La utilización, copia o divulgación de los mismos por parte de alguien diferente a dicho destinatario no está permitida sin autorización. Si ha recibido este mensaje por error, le rogamos que lo comunique por esta misma vía y seguidamente lo destruya.***


Re: update channel selector

José Manuel Delicado Alcolea
 

Hi Brian,

I'm the writter of Update Channel Selector. I don't know where you read that it causes crashes even when it is not present, but this is completely false. The problem of portable copies is being discussed on issue 5 of Update Channel Selector repo, so there is no need to have two parallel conversations about the same topic, specially when the second one includes false statements.

Regards.


El 11/06/2022 a las 11:11, Brian's Mail list account via groups.io escribió:
I noticed on the issues tracker that somebody  has pointed out that if this add on has been used but even if its no longer present, it can cause crashes due to entries in the config file of nvda when creating a portable copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to remove any changes  or maybe NVDA itsself should do so, before creating a portable copy.
Brian

--

José Manuel Delicado Alcolea
Equipo de gestión web y desarrollo



Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2001
- jm.delicado@...
- www.NVDA.es
- @nvda_es

***Este mensaje y sus adjuntos están dirigidos a su destinatario y pueden contener información exclusiva o confidencial. La utilización, copia o divulgación de los mismos por parte de alguien diferente a dicho destinatario no está permitida sin autorización. Si ha recibido este mensaje por error, le rogamos que lo comunique por esta misma vía y seguidamente lo destruya.***


update channel selector

Brian's Mail list account
 

I noticed on the issues tracker that somebody has pointed out that if this add on has been used but even if its no longer present, it can cause crashes due to entries in the config file of nvda when creating a portable copy of the latest alphas.
Maybe the writer of that add on might need to think about a way to remove any changes or maybe NVDA itsself should do so, before creating a portable copy.
Brian

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


Re: Telegram group for discussing NVDA addons development topics

René Linke
 

Oh sorry, I forgot that Ungiram can be installed from the Microsoft Windows-Store, too.


Re: Telegram group for discussing NVDA addons development topics

René Linke
 

Hi William,

Telegram is accessible if you are using it on a computer via Tweesecake or Unigram App for Windows and UnigramPlus add-on for NVDA.
In iOS, it is just in some points accessible, but it is getting slowly better.
Don't use the Telegram Desktop App for Windows, that isn't accessible at all with NVDA.

Tweesecake can be found here (no NVDA add-ons needed):
https://tweesecake.app/

The Unigram App for Windows can be found here:
https://github.com/UnigramDev/Unigram

And the UnigramPlus add-on for NVDA from here:
https://t.me/unigramPlus/57

If you want to use the add-on, don't forget to enable the checkbox for checking on UnigramPlus updated when NVDA starts. It is disabled by default.
Then you will get a message box automatically if there is an update where you can just click on the Yes button to install it.

cheers,
René

681 - 700 of 19738