Date   

Re: NVDA add-ons community announcements: legacy add-ons page update, community add-ons website will remove add-on dev guide

Brian's Mail list account
 

Also, I have noted recently that I am getting an increased number of old xp machines to put the old version of nvda onto. Now I know all the warnings but that is probably not the point, as in most cases these machines are being used off line and mainly for writing documents etc, so I've been looking for add ons for nvda 2017.x ie the last version to work on xp. If you are tidying things up, it might be an idea to see if anyone has the main useful ones and making a kind of lost archive, section.
Brian

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

----- Original Message -----
From: "Noelia Ruiz" <nrm1977@...>
To: <nvda-devel@groups.io>
Sent: Saturday, August 15, 2020 3:30 AM
Subject: Re: [nvda-devel] NVDA add-ons community announcements: legacy add-ons page update, community add-ons website will remove add-on dev guide


Hi, also, the development guide is mentioned now in NVDA readme file.
A link to internals is provided. I think people maybe confused when we
use NVDA development guide for the community guide (writen almost
completely by you) and the NV Access guide. I think this should be
always named Community development guide, or maybe unified with the
guide writen by NV Access when the future add-on store is out, since
then you may include a section about add-ons submision, with add-on
template or other system that can be used (for instance, the add-on
template may be a submodule use only in GitHub Actions, without the
needing to keep all files in each individual repo, just imagining a
possibility). I think that using a link labeled add-on internals is
agood idea so that people don't get confussed between NV Access and
community material, which may have different purposes and history.
Also, speech player in espeak is incompatible and listed in the
development website. And I'm not sure about online image described by
Larry Wann, an excellent add-on who included Image Described by
Oliver. So I think that the website needs to be reviewed carefully, at
least when the store submission for add-ons is out. I suppose that
add-ons have to be quickly reviewed to decide about them and which is
the best section for each one. I'm not sure, sincerely.

2020-08-14 23:48 GMT+02:00, Joseph Lee <@joslee>:
Hello everyone,

A version of this announcement will be sent to NVDA users soon.

The following announcement stems from a discussion regarding now deprecated
Image Describer add-on on NVDA add-ons mailing list (the add-on is no
longer
working):

As many of you may know, there exist two pages on community add-ons website
that are not mentioned frequently:

* Legacy add-ons page, listing add-ons no longer considered compatible
with recent NVDA releases.
* Add-on development guide, which used to provide information on
add-on development basics.

A few weeks ago a situation arose where an add-on advertised itself as
compatible with not that old NVDA release stopped functioning. The NVDA
add-ons community learned that this add-on, Image Describer, relied on a
service that the add-on author did not have access to (specifically, no
payment). Because the bulk of the add-on didn't even work, the community
considered removing it from community add-ons website.

While investigating this, the legacy add-ons page was found to contain
references to NVDA 2019.3, which wasn't really future-proof. Although for
now mentioning 2019.3 as a backwards incompatible release is fine, NV
Access
noted a couple times that API's used by add-ons marked for deprecation will
be removed annually (the next such occurrence may happen early next year).
Therefore, the legacy add-ons page will now state that the page will list
add-ons considered incompatible with more recent NVDA releases, with an
option to state latest backwards incompatible NVDA release for many
add-ons.

In regards to add-on development guide, it is a bit complicated. Originally
the community add-ons site hosted this guide because there was no better
place to host this document when it first appeared in late 2013. I have
marked this document as untranslatable, but due to the translation
workflow,
it was translated (which benefited some language communities as a result).
In recent years, with the advent of NVDA Add-ons organization on GitHub,
add-on development guide found a better home: NVDA Add-ons development
wiki.
With new material added to GitHub wiki page, the dev guide hosted on
community add-ons site naturally ended up becoming horribly outdated.

Therefore, the add-on dev guide hosted on community add-ons website will be
removed. This will be done in stages:

1. No later than August 31, 2020: add-on dev guide page hosted on
community add-ons site will provide a link to the official add-on dev guide
page found on GitHub, nothing else.
2. The day NVDA 2021.1 is released: dev guide page hosted on community
add-ons website will be deleted permanently.



Thank you.

Cheers,

Joseph





Re: NVDA add-ons community announcements: legacy add-ons page update, community add-ons website will remove add-on dev guide

Noelia Ruiz
 

Hi, also, the development guide is mentioned now in NVDA readme file.
A link to internals is provided. I think people maybe confused when we
use NVDA development guide for the community guide (writen almost
completely by you) and the NV Access guide. I think this should be
always named Community development guide, or maybe unified with the
guide writen by NV Access when the future add-on store is out, since
then you may include a section about add-ons submision, with add-on
template or other system that can be used (for instance, the add-on
template may be a submodule use only in GitHub Actions, without the
needing to keep all files in each individual repo, just imagining a
possibility). I think that using a link labeled add-on internals is
agood idea so that people don't get confussed between NV Access and
community material, which may have different purposes and history.
Also, speech player in espeak is incompatible and listed in the
development website. And I'm not sure about online image described by
Larry Wann, an excellent add-on who included Image Described by
Oliver. So I think that the website needs to be reviewed carefully, at
least when the store submission for add-ons is out. I suppose that
add-ons have to be quickly reviewed to decide about them and which is
the best section for each one. I'm not sure, sincerely.

2020-08-14 23:48 GMT+02:00, Joseph Lee <@joslee>:

Hello everyone,

A version of this announcement will be sent to NVDA users soon.

The following announcement stems from a discussion regarding now deprecated
Image Describer add-on on NVDA add-ons mailing list (the add-on is no
longer
working):

As many of you may know, there exist two pages on community add-ons website
that are not mentioned frequently:

* Legacy add-ons page, listing add-ons no longer considered compatible
with recent NVDA releases.
* Add-on development guide, which used to provide information on
add-on development basics.

A few weeks ago a situation arose where an add-on advertised itself as
compatible with not that old NVDA release stopped functioning. The NVDA
add-ons community learned that this add-on, Image Describer, relied on a
service that the add-on author did not have access to (specifically, no
payment). Because the bulk of the add-on didn't even work, the community
considered removing it from community add-ons website.

While investigating this, the legacy add-ons page was found to contain
references to NVDA 2019.3, which wasn't really future-proof. Although for
now mentioning 2019.3 as a backwards incompatible release is fine, NV
Access
noted a couple times that API's used by add-ons marked for deprecation will
be removed annually (the next such occurrence may happen early next year).
Therefore, the legacy add-ons page will now state that the page will list
add-ons considered incompatible with more recent NVDA releases, with an
option to state latest backwards incompatible NVDA release for many
add-ons.

In regards to add-on development guide, it is a bit complicated. Originally
the community add-ons site hosted this guide because there was no better
place to host this document when it first appeared in late 2013. I have
marked this document as untranslatable, but due to the translation
workflow,
it was translated (which benefited some language communities as a result).
In recent years, with the advent of NVDA Add-ons organization on GitHub,
add-on development guide found a better home: NVDA Add-ons development
wiki.
With new material added to GitHub wiki page, the dev guide hosted on
community add-ons site naturally ended up becoming horribly outdated.

Therefore, the add-on dev guide hosted on community add-ons website will be
removed. This will be done in stages:

1. No later than August 31, 2020: add-on dev guide page hosted on
community add-ons site will provide a link to the official add-on dev guide
page found on GitHub, nothing else.
2. The day NVDA 2021.1 is released: dev guide page hosted on community
add-ons website will be deleted permanently.



Thank you.

Cheers,

Joseph





NVDA add-ons community announcements: legacy add-ons page update, community add-ons website will remove add-on dev guide

 

Hello everyone,

A version of this announcement will be sent to NVDA users soon.

The following announcement stems from a discussion regarding now deprecated Image Describer add-on on NVDA add-ons mailing list (the add-on is no longer working):

As many of you may know, there exist two pages on community add-ons website that are not mentioned frequently:

  • Legacy add-ons page, listing add-ons no longer considered compatible with recent NVDA releases.
  • Add-on development guide, which used to provide information on add-on development basics.

A few weeks ago a situation arose where an add-on advertised itself as compatible with not that old NVDA release stopped functioning. The NVDA add-ons community learned that this add-on, Image Describer, relied on a service that the add-on author did not have access to (specifically, no payment). Because the bulk of the add-on didn’t even work, the community considered removing it from community add-ons website.

While investigating this, the legacy add-ons page was found to contain references to NVDA 2019.3, which wasn’t really future-proof. Although for now mentioning 2019.3 as a backwards incompatible release is fine, NV Access noted a couple times that API’s used by add-ons marked for deprecation will be removed annually (the next such occurrence may happen early next year). Therefore, the legacy add-ons page will now state that the page will list add-ons considered incompatible with more recent NVDA releases, with an option to state latest backwards incompatible NVDA release for many add-ons.

In regards to add-on development guide, it is a bit complicated. Originally the community add-ons site hosted this guide because there was no better place to host this document when it first appeared in late 2013. I have marked this document as untranslatable, but due to the translation workflow, it was translated (which benefited some language communities as a result). In recent years, with the advent of NVDA Add-ons organization on GitHub, add-on development guide found a better home: NVDA Add-ons development wiki. With new material added to GitHub wiki page, the dev guide hosted on community add-ons site naturally ended up becoming horribly outdated.

Therefore, the add-on dev guide hosted on community add-ons website will be removed. This will be done in stages:

  1. No later than August 31, 2020: add-on dev guide page hosted on community add-ons site will provide a link to the official add-on dev guide page found on GitHub, nothing else.
  2. The day NVDA 2021.1 is released: dev guide page hosted on community add-ons website will be deleted permanently.

 

Thank you.

Cheers,

Joseph


Re: NVDA does not read list items in SpeedCommander, if the view is set to thumbnails or icons

 

Hello all,

I've updated to the latest alpha snapshot of NVDA and the problem is fixed. I think the fix for #11468 fixed the problem in SpeedCommander as well. So, thanks for the fix.

______
Best wishes,
Kostadin Kolev

На 4.8.2020 г. в 16:51, Kostadin Kolev написа:

Hello all,

Me and the main developer of SpeedCommander - Sven Ritter - are continuing our conversation about this issue. We've found some things, which I'm posting here. As Sven said, maybe the developers of NVDA can assist in solving this issue. Here's the conversation:

======

Sven Ritter:

in the log file I noticed the following lines:

DEBUGWARNING - NVDAObjects.IAccessible.sysListView32.ListItem._getColumnLocationRaw (20:05:59.637) - MainThread (1780):
LVM_GETSUBITEMRECT failed for index 3 in list

LVM_GETSUBITEMRECT only makes sense in the detail view. It returns the areas for the individual column elements. In the symbol view these do not exist and therefore it makes no sense to query them.

Please check if deactivating „Display columns in all views" in the settings dialog on the „View - Appearance" page helps. Maybe NVDA is irritated by this extended list view style option (LVS_EX_HEADERINALLVIEWS).


Me:

I've disabled "Display columns in all views" in View ➡ Appearance in SpeedCommander. Unfortunately however, this did not fix the issue.

You may have a point however that it is related to columns from the details view. NVDA has commands (Control+Alt+Arrow keys) to move between columns and rows in tables and details view in lists. When I use Control+Alt+Left/Right arrows to navigate between columns for the current row, it works even for the thumbnails view. That is useful to me, but it is unusual/non-standard behavior. But even after I disabled "Display columns in all views", NVDA's behavior with the Control+Alt+Arrow keys remained the same - even in thumbnails view it behaved as if the focus was in a details view. So, maybe SpeedCommander's "Display columns in all views" option displays/hides the columns only visually and not on a deeper (programmatic) level.

Apparently, there is a strange lack of cooperation between NVDA and SpeedCommander in thumbnails/icons view. Strangely enough, I'm almost 100% sure that it worked as it should in v18 of SpeedCommander. Were any changes done to that component of SpeedCommander in v19?


Sven Ritter:

there are only some minor changes in the list view control, mainly refactoring stuff and for dark mode support.

Can you please download and install SC18 to check it? Both versions can be used side by side.

Me:

I've installed SpeedCommander 18 and with it I don't have the problem - NVDA reads the list items even if they are in a thumbnails or icons view.

But with it I also cannot navigate with Control+Alt+Arrow keys between column items in thumbnails and icons view. Again, Control+Alt+Arrow keys is an NVDA command for navigating between table columns and rows, which also works for list views in details view. More precisely, using Control+Alt+Left/Right arrow keys reports that I'm at the end of the table and Control+Alt+Up/Down arrow keys moves between the previous and next item in the list. That means that SpeedCommander 18 presents such views as tables with 1 column and number of rows corresponding to the number of items in the list. Unlike SpeedCommander 19, which presents even thumbnails and icons views as tables and the columns from the details view are only visually hidden but programmatically (including for screen readers) visible.


Sven Ritter:

I found some time today and experimented a little. And here's what I discovered:

1) During the first test under Windows 10 with SpeedCommander 19, NVDA had no problems reading the items in the thumbnail view.

2) After updating NVDA to the current version 2020.2 no more items were recognized. So far I had 2019.2 installed.

3) In SpeedCommander 19 the list view is created explicitly in detail view mode. This is necessary to display the column header correctly in dark mode. After the window creation, the program switches to the desired mode. This is analogous to SpeedCommander 18, where the list is created in symbol view mode.

4) If I create the list view in SpeedCommander 19 in symbol mode, the recognition of the items also works with NVDA 2020.2.

5) Since it worked with NVDA 2019.2, I have downgraded NVDA step by step (2020.1, 2019.3, 2019.2.1). With version 2019.2.1 it works again, even switching between column entries via Ctrl+Alt+cursor keys.

So there must be a change between 2019.2 and 2019.3 in NVDA that prevents the recognition of items in the thumbnail view when the list view is first created in column mode.

In the release notes for 2019.3 I found the following bug fix:

NVDA will no longer report content of visually hidden columns for list items in SysListView32 controls. (#8268)

Possibly this change is the reason for the incorrect behaviour. The github item

https://github.com/nvaccess/nvda/issues/8268

contains the title

sysListView32.ListItem._getColumnLocationRaw can return malformed rectangles (i.e. with a left coordinate that is greaterher than the right coordinate)

It is probably no coincidence that _getColumnLocationRaw also appears in your log file.

Maybe the NVDA developers can do something with it.

======

Thanks in advance!

______
Best wishes,
Kostadin Kolev

На 21.7.2020 г. в 15:22, Kostadin Kolev написа:

Hello Alberto,

I tried maximizing the window, but that did not help. And why in this case even Narrator does not have a problem in reading the items (?). So I doubt it is due to the window not being maximized. Besides that, in its current size, the window of SpeedCommander shows a view of 4 columns and 4 rows of thumbnails, which I think is more than enough for a proper displaying of the items in the view.

As for the portable NVDA. That is a portable copy of the stable NVDA release, which I have for test purposes. I have an installed copy of the latest alpha snapshot and the problem is the same.

______
Best wishes,
Kostadin Kolev

На 21.7.2020 г. в 11:53, Alberto Buffolino написа:
Kostadin Kolev, il 21/07/2020 10.44, ha scritto:
Has the quoted message below arrived to the list? Because it is 3 days since I've sent it and there has been no reply to it it all. It contained an attachment - are they allowed on this list?
Alberto:
Hi Kostadin,
yes, it arrived, with attachment.
According to log, I suggest to try:
1) to maximize window (object name shows an exception about object dimensions, so it's not read);
2) to install NVDA, recomended for stable use in various scenarious.
Alberto




Re: translation rule book

Brian's Mail list account
 

This looks like one for the translation list, but I don't keep it myself, anyone?
Brian

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

----- Original Message -----
From: "tsuji takahiro" <tsuji.tsujit.takahiro813@...>
To: <nvda-devel@groups.io>
Sent: Thursday, August 06, 2020 12:36 AM
Subject: [nvda-devel] translation rule book


Hello,

I am a Japanese software engineer and have been using NVDA.
If possible, can you tell me the name of the rule book which you are based
on?
For example, 点字表記法、点訳のてびき etc.

Regards,
Takahiro


Re: Selection re-appears when editing file names in explorer

Brian's Mail list account
 

Well I do notice sometimes some lag in what nvda thinks is selected and what actually is sometimes. I put this down to UIA issues. Its even there in windows 7 if you have a large folder or several folders open at once.
Not sure where the problem lies but the same thing occurs if scrolling up and down, and then copy a file you often end up with the wrong file!
Brian

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

----- Original Message -----
From: "Karl-Otto Rosenqvist" <Karl-otto@...>
To: <nvda-devel@groups.io>
Sent: Wednesday, August 05, 2020 9:12 PM
Subject: [nvda-devel] Selection re-appears when editing file names in explorer


Hi!
Is it only my machine that¨s behaving stupid or does anyone else see this?
Sometimes when I press F2 to edit a file name in explorer and I press left arrow so the selection disappears and the cursor moves to the start of the file name the file name gets selected automatically again. Regardless of how I make the selection disappear it appears immediately again.
If you're not aware that this happens you'll overwrite the original file name and probably the text you just wrote too.

Is this NVDA or Explorer that missbehaves?


Kind regards

Karl-Otto
--
Karl-Otto Rosenqvist
MAWINGU
Orgnr: 750804-3937
+46 (0)701 75 98 56
karl-otto@...


Re: get picture content of diagram

Shubham Jain
 

Hi Tage,

I'm not sure if it's the best way to do this but this is how I am doing something similar for my add-ons:

import screenBitmap
left, top, width, height = nav.location    #where nav is your navigator object with role ROLE_DIAGRAM
sb = screenBitmap.ScreenBitmap(width, height)
pixels = sb.captureImage(left, top, width, height)    #will give you a 2D array of RBGAQuad values

# If you want to save the image as a file you can do the following
import wx
bmp = wx.EmptyBitmap(width, height, 32)
bmp.CopyFromBuffer(pixels, wx.BitmapBufferFormat_RGB32)
bmp.SaveFile("path_to_save_location.jpg", wx.BITMAP_TYPE_JPEG)    # you can also use different image formats instead of JPEG (see here)

regards,
Shubham Jain


translation rule book

tsuji takahiro
 

Hello,

I am a Japanese software engineer and have been using NVDA.
If possible, can you tell me the name of the rule book which you are based on?
For example, 点字表記法、点訳のてびき etc.

Regards,
Takahiro


Re: Selection re-appears when editing file names in explorer

James Scholes
 

Does this happen in all folders? I've seen it happen in Dropbox, presumably because the Dropbox shell extension is doing something wrong behind the scenes (or something right and its Windows's fault). Either way, it doesn't happen everywhere.

Regards,

James Scholes

On 05/08/2020 at 3:12 pm, Karl-Otto Rosenqvist wrote:
Hi!
Is it only my machine that¨s behaving stupid or does anyone else see this?
Sometimes when I press F2 to edit a file name in explorer and I press left arrow so the selection disappears and the cursor moves to the start of the file name the file name gets selected automatically again. Regardless of how I make the selection disappear it appears immediately again.
If you're not aware that this happens you'll  overwrite the original file name and probably the text you just wrote too.
Is this NVDA or Explorer that missbehaves?
Kind regards
Karl-Otto


get picture content of diagram

Tage Johansson <frans.tage@...>
 

Hello,


I have an object with the role ROLE_DIAGRAM. How can I retreeve the actual picture of the diagram. Or so to say, the pixels on the window corresponding to the object.


It is in firefox if that helps.


Thanks in advance,

Tage


Selection re-appears when editing file names in explorer

Karl-Otto Rosenqvist
 

Hi!
Is it only my machine that¨s behaving stupid or does anyone else see this?
Sometimes when I press F2 to edit a file name in explorer and I press left arrow so the selection disappears and the cursor moves to the start of the file name the file name gets selected automatically again. Regardless of how I make the selection disappear it appears immediately again.
If you're not aware that this happens you'll overwrite the original file name and probably the text you just wrote too.

Is this NVDA or Explorer that missbehaves?


Kind regards

Karl-Otto
--
Karl-Otto Rosenqvist
MAWINGU
Orgnr: 750804-3937
+46 (0)701 75 98 56
karl-otto@...


Does NVDA not work with WPF Textbox and Rich text edit controls?

Tom Kingston
 

I’m writing a WPF app and with speak typed characters off and speak typed words on nothing is spoken in these controls until I enter a punctuation mark. For example, if I type an entire sentence with no punctuation nothing is spoken until I enter a period at the end. Then the sentence is spoken, but words are broken. Any punctuation within the sentence triggers the same reaction with what I’ve typed up to that point.

I downloaded the entire sample archive from Microsoft’s GitHub site and see the same behavior with their apps.

These controls work fine with Narrator and Window-Eyes.

Thanks,

Tom

 

 


Re: NVDA does not read list items in SpeedCommander, if the view is set to thumbnails or icons

 

Hello all,

Me and the main developer of SpeedCommander - Sven Ritter - are continuing our conversation about this issue. We've found some things, which I'm posting here. As Sven said, maybe the developers of NVDA can assist in solving this issue. Here's the conversation:

======

Sven Ritter:

in the log file I noticed the following lines:

DEBUGWARNING - NVDAObjects.IAccessible.sysListView32.ListItem._getColumnLocationRaw (20:05:59.637) - MainThread (1780):
LVM_GETSUBITEMRECT failed for index 3 in list

LVM_GETSUBITEMRECT only makes sense in the detail view. It returns the areas for the individual column elements. In the symbol view these do not exist and therefore it makes no sense to query them.

Please check if deactivating „Display columns in all views" in the settings dialog on the „View - Appearance" page helps. Maybe NVDA is irritated by this extended list view style option (LVS_EX_HEADERINALLVIEWS).


Me:

I've disabled "Display columns in all views" in View ➡ Appearance in SpeedCommander. Unfortunately however, this did not fix the issue.

You may have a point however that it is related to columns from the details view. NVDA has commands (Control+Alt+Arrow keys) to move between columns and rows in tables and details view in lists. When I use Control+Alt+Left/Right arrows to navigate between columns for the current row, it works even for the thumbnails view. That is useful to me, but it is unusual/non-standard behavior. But even after I disabled "Display columns in all views", NVDA's behavior with the Control+Alt+Arrow keys remained the same - even in thumbnails view it behaved as if the focus was in a details view. So, maybe SpeedCommander's "Display columns in all views" option displays/hides the columns only visually and not on a deeper (programmatic) level.

Apparently, there is a strange lack of cooperation between NVDA and SpeedCommander in thumbnails/icons view. Strangely enough, I'm almost 100% sure that it worked as it should in v18 of SpeedCommander. Were any changes done to that component of SpeedCommander in v19?


Sven Ritter:

there are only some minor changes in the list view control, mainly refactoring stuff and for dark mode support.

Can you please download and install SC18 to check it? Both versions can be used side by side.

Me:

I've installed SpeedCommander 18 and with it I don't have the problem - NVDA reads the list items even if they are in a thumbnails or icons view.

But with it I also cannot navigate with Control+Alt+Arrow keys between column items in thumbnails and icons view. Again, Control+Alt+Arrow keys is an NVDA command for navigating between table columns and rows, which also works for list views in details view. More precisely, using Control+Alt+Left/Right arrow keys reports that I'm at the end of the table and Control+Alt+Up/Down arrow keys moves between the previous and next item in the list. That means that SpeedCommander 18 presents such views as tables with 1 column and number of rows corresponding to the number of items in the list. Unlike SpeedCommander 19, which presents even thumbnails and icons views as tables and the columns from the details view are only visually hidden but programmatically (including for screen readers) visible.


Sven Ritter:

I found some time today and experimented a little. And here's what I discovered:

1) During the first test under Windows 10 with SpeedCommander 19, NVDA had no problems reading the items in the thumbnail view.

2) After updating NVDA to the current version 2020.2 no more items were recognized. So far I had 2019.2 installed.

3) In SpeedCommander 19 the list view is created explicitly in detail view mode. This is necessary to display the column header correctly in dark mode. After the window creation, the program switches to the desired mode. This is analogous to SpeedCommander 18, where the list is created in symbol view mode.

4) If I create the list view in SpeedCommander 19 in symbol mode, the recognition of the items also works with NVDA 2020.2.

5) Since it worked with NVDA 2019.2, I have downgraded NVDA step by step (2020.1, 2019.3, 2019.2.1). With version 2019.2.1 it works again, even switching between column entries via Ctrl+Alt+cursor keys.

So there must be a change between 2019.2 and 2019.3 in NVDA that prevents the recognition of items in the thumbnail view when the list view is first created in column mode.

In the release notes for 2019.3 I found the following bug fix:

NVDA will no longer report content of visually hidden columns for list items in SysListView32 controls. (#8268)

Possibly this change is the reason for the incorrect behaviour. The github item

https://github.com/nvaccess/nvda/issues/8268

contains the title

sysListView32.ListItem._getColumnLocationRaw can return malformed rectangles (i.e. with a left coordinate that is greaterher than the right coordinate)

It is probably no coincidence that _getColumnLocationRaw also appears in your log file.

Maybe the NVDA developers can do something with it.

======

Thanks in advance!

______
Best wishes,
Kostadin Kolev

На 21.7.2020 г. в 15:22, Kostadin Kolev написа:

Hello Alberto,

I tried maximizing the window, but that did not help. And why in this case even Narrator does not have a problem in reading the items (?). So I doubt it is due to the window not being maximized. Besides that, in its current size, the window of SpeedCommander shows a view of 4 columns and 4 rows of thumbnails, which I think is more than enough for a proper displaying of the items in the view.

As for the portable NVDA. That is a portable copy of the stable NVDA release, which I have for test purposes. I have an installed copy of the latest alpha snapshot and the problem is the same.

______
Best wishes,
Kostadin Kolev

На 21.7.2020 г. в 11:53, Alberto Buffolino написа:
Kostadin Kolev, il 21/07/2020 10.44, ha scritto:
Has the quoted message below arrived to the list? Because it is 3 days since I've sent it and there has been no reply to it it all. It contained an attachment - are they allowed on this list?
Alberto:
Hi Kostadin,
yes, it arrived, with attachment.
According to log, I suggest to try:
1) to maximize window (object name shows an exception about object dimensions, so it's not read);
2) to install NVDA, recomended for stable use in various scenarious.
Alberto




NVDA contribution guide: so you want to submit a pull request...

 

Hi all,

 

While editing the latest edition of NVDA Add-on Dev Guide and in the midst of planning a pull request strategy, I thought about something that was nagging at the back of my mind and I’m sure many are wondering about: submitting pull requests. This stems from a discussion on NVDA add-ons list several weeks ago regarding add-on development strategies such as code layout and such. I hope the following serves as sort of a rough map as to how to navigate the complex landscape of pull requests for any project, specifically for NVDA.

 

One of the reasons why NVDA is popular is because people can suggest and submit changes publicly. Sometimes this is needed to keep up with technology and accessibility standards. Sometimes a braille display manufacturer would like to see drivers for their products integrated into NVDA. Sometimes people submit spelling and grammar fixes for documentation. Whatever the suggestion might be, they go through a review process – the moment a pull request is submitted, it goes through several checks, culminating in improving your work based on feedback from stable version users (I’ll talk about this phrasing later, as that is going to be important).

 

Some of you might be wondering what a pull request is. A pull request is the act of submitting changes you made to a piece of software for inclusion in the original product. It starts with you thinking about an idea, a change, or a bug, then you go through researching, coding, and testing your idea, and if you believe your idea is ready for the world, publish a pull request. The maintainer of the product you are sending a pull request for would review your idea, suggest improvements if any, and if things are looking fine, integrate it into the original product.

 

No, forget the above definition. In truth, a pull request is a collection of your thought process, research and coding skills, test cases, real-world (and sometimes hypothetical) justifications, user impact, empathy and communication, refinements, feedback, and life-long learning. A successful pull request contains ALL of these. For example, a pull request is not complete without impactful justifications, code without tests will come back to haunt you years later, and your brilliant fix becomes meaningless when you don’t show empathy and effective communication skills.

 

So I guess some of you might insist on writing pull requests. There is one more thing that makes or breaks a pull request: do you understand the project itself? I don’t want you to think that code is everything – beginning computer science and software engineering students may think that coding is all there is to it. A project, as a complete system, contains not only code, but personnel, history, culture, assumptions, norms, expectations, and impact. This is more so for a specialized project such as NVDA: screen reader users have different expectations about what it means to use computers and using software. For instance, one of the cultural artifacts of NVDA is keyboard accessibility, which is different than say, a touch-based user interface. After these warnings, if you are not willing to or not comfortable with learning to appreciate screen reading, cultural assumptions about disability, and accessibility norms, then I’m afraid that writing pull requests for NVDA might not be a good idea for you at this time.

 

I’m saying all these (in a long way) to give you this solemn warning: without understanding the context in which NVDA operates (computer accessibility and usability for people with disabilities), writing effective NVDA pull requests is impossible. Sure, we (NVDA developers and code contributors) look for coding style, test cases, and good justifications when reviewing pull requests. But what we are after is your willingness to understand the culture in which NVDA is used. Do not give us a brilliant algorithm that can solve hundreds of different IAccessible2 issues at once. Rather, let us know that you are learning the NVDA source code and culture.

 

So how do you write an effective NVDA pull request? Well, the second step is thinking carefully (the first step was the above warning). After being part of NVDA community and culture for a while (obviously you need to be familiar with bits of NVDA source code and coding style), you may come across an interesting idea, a user suggestion or two, or perhaps you found an ancient bug. Do not be tempted to start coding right away – sit down, get a drink (not alcohol please), and think about what you just heard or discovered (the latter in case you found a bug). Depending on what’s bothering you, you can think about the following:

 

  • Someone suggested something. How can I better understand what this person is talking about? If you want, start talking to the person who suggested such and such change.
  • I discovered a bug. Do I understand what this bug might be (or what the bug is), or is this something wrong with my NVDA settings? If it is truly an ancient bug, how can I reproduce it, and are there potential causes, impact, and solutions?
  • I have this brilliant idea I want to test. Can I articulate it to NVDA beginners? How can I test this idea? What will its impact be for users? What potential issues can it cause?

 

But don’t just think aloud to yourself: talk to someone. The best way to do so is searching GitHub, and if you know the idea you have (or a bug you found) wasn’t found, file a new issue. Chances are that someone will talk to you through various means (including commenting on the issue you filed); after all, humans are social beings.

 

So you talked to someone, and either you know you’re going to work on this idea or may get help from someone (or perhaps artificial intelligence might come to the rescue). If you are comfortable (and confident) enough to work on researching, coding, testing, explaining, and justifying your idea, go ahead with research, coding, and testing. Do not spend all night coding (trust me, I and many others have gone through countless all-night hackathons and regretted afterwards).

 

When you research, code, and test your idea (which may or may not become your dream pull request), keep the following in mind:

 

  • You need to read a lot. You need to prepare your mind so that when it comes time to code and test, you will know what you are up to.
  • You are writing an essay. After all, coding is responding to an essay prompt (or two).
  • You are teaching a machine to think differently. You are a movie director, an architect, a tutor, a politician (maybe that’s going too far), or any job that requires you to teach someone (or something) new skills.
  • Don’t forget to “taste your wine”. An effective software is not complete without extensive tests. And no, just compiling and running your changes does not constitute a complete test – you MUST try your best to comply with pull request expectations (including, yes, linting BEFORE you commit).
  • You are a user, after all. In other words, perform tests as though you are the person who suggested the idea you are “talking” about in your code.

 

After you think, research, code, and test your idea (or a pull request), and verifying that it is ready to be sent to NV Access for review (via GitHub), prepare to explain and justify your changes. An effective pull request is more subjective than objective. That is, how you explain and justify your changes will have great impact on acceptance of your pull request. For example, if you just tell NVDA Developers that you fixed an ancient bug without specifying what it is or how you did it, reviewers might say, “hmmm, tell us more.” Or you come up with a brilliant algorithm for fixing hundreds of IAccessible2 issues at once but do not justify the impact of your algorithm on users. The overwhelming response will be, “how will your idea affect users as they use NVDA in hundreds of different scenarios?” Or in some cases, you submit a pull request based on a user’s suggestion, thinking that it is in scope for screen reading. How reviewers react to that pull request will depend on how effective your justifications are going to be (after all, persuasion matters).

 

At some point, reviewers will review your work and either approve your idea, suggest changes, or direct you elsewhere. Do not worry if reviewers tell you that your idea does not fit NVDA and its culture; think of that decision as a way for you to reflect on your thought process. If reviewers suggest changes, think about what these are and respond accordingly (perhaps make suggested changes, discuss changes, or something else).

 

Now your pull request has been approved and integrated into NVDA. This is not the time to pop open that champagne bottle you kept for this purpose. Rather, prepare to receive feedback from users, even when your idea makes it to the next public release of NVDA. This is so that you can learn and refine your work. Also, if you are willing, take some time to help others with their pull requests (reviewing, suggesting things, researching on behalf of others if asked, or drop some occasional joke or two (joking)).

 

I did briefly mention humor as an interesting way to help others. I included it to highlight the serious and rigorous nature of writing and submitting NVDA pull requests. NVDA development through pull requests is a serious and rigorous process, as a small change you make will be used in many scenarios by thousands of users around the world. More importantly, as a seasoned code contributor (I joined NVDA community in 2012), the most important thing you should learn is understanding the culture (disability culture) in which NVDA operates – I want you to become advocates, not just programmers.

 

Before I forget: some of you might be wondering about NVDA add-on development. Although not as rigorous as NVDA itself, you should take that process seriously, as your add-on(s) will be used by many people.

 

For me, among recent pull requests I wrote, the one I’m proud of is introducing foundations to support UIA notification event. It took me days to understand the scope of the problem and work on a stable solution. The pull request that brought you UIA notification event support was merged in 2018, and we have seen refinements since.

 

Perhaps the most intriguing pull request I submitted was ability to enable and disable individual add-ons. I spent days trying to understand the internal logic required to support this scenario. I received feedback from many people on this regard, including from several core NVDA developers. Ever since this pull request was merged in 2016, many improvements were made, some of which I provided feedback on.

 

I’m sure many of you would like to contribute to NVDA for months and years to come (including for the eventual new developer hired by NV Access). But remember my warning above: coding, specifically writing and submitting pull requests is not for everyone. Writing and submitting pull requests is a serious and rigorous task, and if you are not willing to learn the culture surrounding NVDA, your pull requests will not be effective. I and other developers can teach you the inner workings of NVDA for weeks to months (or years), but it is up to potential pull request writers themselves to show willingness to make an impactful difference for a community who must now rely on the double-edged sword that is technological progress, especially given the era we live in.

 

To those writing pull requests, good luck. To those contributing in other ways, keep up the good work. Please stay safe and healthy.

Cheers,

Joseph


Re: Question for NV Access staff: Can we share the direct link to download NVDA?

Brian's Mail list account
 

Its a shame that all these services which supposedly translate web sites could not actually allow buttons to be pressed.
Brian

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

----- Original Message -----
From: "Noelia Ruiz" <nrm1977@...>
To: <nvda-devel@groups.io>
Sent: Thursday, July 30, 2020 4:32 AM
Subject: Re: [nvda-devel] Question for NV Access staff: Can we share the direct link to download NVDA?


Thanks, I have updated our spanish website at nvdaes.github.io
accordingly, including the direct download link in the header of the
website after its description and before the search form, and also in
the post related to NVDA 2020.2, in this case, providing a link to
this thread about the download procedure preferred by NV Access.
Please let us know if we should change the form of the download URL in
a future moment so you can gatter stats or whatever.
I think I have seen several times on mailing lists a different URL
with the word file.
Noelia

2020-07-29 23:14 GMT+02:00, Michael Curran <mick@...>:
If you use a url of the following form, we will still be able to gather
download stats:

http://www.nvaccess.org/download/nvda/releases/2020.2/nvda_2020.2.exe


Mick


On 30/07/2020 5:22 am, Noelia Ruiz wrote:
I think that it would be useful if the website was translated, maybe
with a warning to clarify that translations are not official but just
informative. Communnities have websites, blogs or social network to
inform users anyway, so I don't know how this can be put all together.
For instance, the add-ons website is localized in several languages,
but communities host add-ons in their own websites in several
languages. So, the concern is: if the translation provided in NV
Access servers is not official, what's the additional value of hosting
a translation on their website? It would be useful if some kind of
endorsement could be provided for the translations hosted in their
website, but I don't know if this is or not possible or what would be
required.
NV Access announced that they would work in the translation system for
NVDA and add-ons. Maybe a chance to take a look on this again?
Here is a closed issue for this:
https://github.com/nvaccess/nvda/issues/6392

2020-07-29 20:52 GMT+02:00, Sean <s.tolstoyevski@...>:
I think it is a deficiency that NVDA's official site only serves in
English.

If WordPress translation templates are shared, I would be happy to
translate the site into Turkish.
Very good at Wordpress i18n.

In addition: it is difficult to generate an analysis with just the
download button click counter. This is a simple thing.
Instead, a token-based download system may be needed.

On 29/07/2020 18:09, Reef Turner wrote:
We would prefer users download NVDA from our site, it helps us
understand
the uptake of a new version (through download stats), and reminds users
to
consider donating (which makes it possible to keep providing NVDA).
Another concern is the longevity of the links, though we have no plans
to
change the way NVDA is stored, we can't guarantee this will always be
true.

That said, we wouldn't want a lack of translation to be the reason
someone
is unable to use the latest version of NVDA.

We suppose that if we don't host the launcher on an external website
or
service, if someone downloads NVDA from this link you can get
statistics
appropriately.
I'm not sure at which point the stats are collected. You are right,
theoretically we could count the stats when the file is accessed, in
practice I have a feeling we don’t do that. I think it is tied to the
download button on the download page. Either way, we get a slightly
different statistic based on checks for updates. In my opinion this is
more useful, it gives a better indication of daily active users.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia
Ruiz
Sent: Wednesday, 29 July 2020 4:27 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Question for NV Access staff: Can we share the
direct link to download NVDA?

Hello, I think this is possible, but do you agree with this practice,
considering that the NV Access download page is not translated and the
donation system is just in English?
We have shared the direct link on the spanish list for NVDA created by
me
at groups.io, but we'd like to be sure that you agree about this
practice.
We suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get
statistics
appropriately.
I haven't posted the direct link to stable version on the website
associated with the mailing list in case you prefer we don't share it.
Can you clarify this?
On the website we say, in Spanish: To download NVDA, go to NV Access
website and then press the DOWNLOAd button, but this maybe tricky:
https://nvdaes.github.io/nvda-2020-2/

Thanks






--


Sean

* Email: seantolstoyevski@...
<mailto:seantolstoyevski@...>
* GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

👨‍🦯 I’m programmer. I coding often Python, sometimes Go and rarely
C++.







Re: Question for NV Access staff: Can we share the direct link to download NVDA?

Noelia Ruiz
 

Thanks, I have updated our spanish website at nvdaes.github.io
accordingly, including the direct download link in the header of the
website after its description and before the search form, and also in
the post related to NVDA 2020.2, in this case, providing a link to
this thread about the download procedure preferred by NV Access.
Please let us know if we should change the form of the download URL in
a future moment so you can gatter stats or whatever.
I think I have seen several times on mailing lists a different URL
with the word file.
Noelia

2020-07-29 23:14 GMT+02:00, Michael Curran <mick@...>:

If you use a url of the following form, we will still be able to gather
download stats:

http://www.nvaccess.org/download/nvda/releases/2020.2/nvda_2020.2.exe


Mick


On 30/07/2020 5:22 am, Noelia Ruiz wrote:
I think that it would be useful if the website was translated, maybe
with a warning to clarify that translations are not official but just
informative. Communnities have websites, blogs or social network to
inform users anyway, so I don't know how this can be put all together.
For instance, the add-ons website is localized in several languages,
but communities host add-ons in their own websites in several
languages. So, the concern is: if the translation provided in NV
Access servers is not official, what's the additional value of hosting
a translation on their website? It would be useful if some kind of
endorsement could be provided for the translations hosted in their
website, but I don't know if this is or not possible or what would be
required.
NV Access announced that they would work in the translation system for
NVDA and add-ons. Maybe a chance to take a look on this again?
Here is a closed issue for this:
https://github.com/nvaccess/nvda/issues/6392

2020-07-29 20:52 GMT+02:00, Sean <s.tolstoyevski@...>:
I think it is a deficiency that NVDA's official site only serves in
English.

If WordPress translation templates are shared, I would be happy to
translate the site into Turkish.
Very good at Wordpress i18n.

In addition: it is difficult to generate an analysis with just the
download button click counter. This is a simple thing.
Instead, a token-based download system may be needed.

On 29/07/2020 18:09, Reef Turner wrote:
We would prefer users download NVDA from our site, it helps us
understand
the uptake of a new version (through download stats), and reminds users
to
consider donating (which makes it possible to keep providing NVDA).
Another concern is the longevity of the links, though we have no plans
to
change the way NVDA is stored, we can't guarantee this will always be
true.

That said, we wouldn't want a lack of translation to be the reason
someone
is unable to use the latest version of NVDA.

We suppose that if we don't host the launcher on an external website
or
service, if someone downloads NVDA from this link you can get
statistics
appropriately.
I'm not sure at which point the stats are collected. You are right,
theoretically we could count the stats when the file is accessed, in
practice I have a feeling we don’t do that. I think it is tied to the
download button on the download page. Either way, we get a slightly
different statistic based on checks for updates. In my opinion this is
more useful, it gives a better indication of daily active users.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia
Ruiz
Sent: Wednesday, 29 July 2020 4:27 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Question for NV Access staff: Can we share the
direct link to download NVDA?

Hello, I think this is possible, but do you agree with this practice,
considering that the NV Access download page is not translated and the
donation system is just in English?
We have shared the direct link on the spanish list for NVDA created by
me
at groups.io, but we'd like to be sure that you agree about this
practice.
We suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get
statistics
appropriately.
I haven't posted the direct link to stable version on the website
associated with the mailing list in case you prefer we don't share it.
Can you clarify this?
On the website we say, in Spanish: To download NVDA, go to NV Access
website and then press the DOWNLOAd button, but this maybe tricky:
https://nvdaes.github.io/nvda-2020-2/

Thanks






--


Sean

* Email: seantolstoyevski@...
<mailto:seantolstoyevski@...>
* GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

👨‍🦯 I’m programmer. I coding often Python, sometimes Go and rarely
C++.







Re: Question for NV Access staff: Can we share the direct link to download NVDA?

Michael Curran
 

If you use a url of the following form, we will still be able to gather download stats:

http://www.nvaccess.org/download/nvda/releases/2020.2/nvda_2020.2.exe


Mick

On 30/07/2020 5:22 am, Noelia Ruiz wrote:
I think that it would be useful if the website was translated, maybe
with a warning to clarify that translations are not official but just
informative. Communnities have websites, blogs or social network to
inform users anyway, so I don't know how this can be put all together.
For instance, the add-ons website is localized in several languages,
but communities host add-ons in their own websites in several
languages. So, the concern is: if the translation provided in NV
Access servers is not official, what's the additional value of hosting
a translation on their website? It would be useful if some kind of
endorsement could be provided for the translations hosted in their
website, but I don't know if this is or not possible or what would be
required.
NV Access announced that they would work in the translation system for
NVDA and add-ons. Maybe a chance to take a look on this again?
Here is a closed issue for this:
https://github.com/nvaccess/nvda/issues/6392

2020-07-29 20:52 GMT+02:00, Sean <s.tolstoyevski@...>:
I think it is a deficiency that NVDA's official site only serves in
English.

If WordPress translation templates are shared, I would be happy to
translate the site into Turkish.
Very good at Wordpress i18n.

In addition: it is difficult to generate an analysis with just the
download button click counter. This is a simple thing.
Instead, a token-based download system may be needed.

On 29/07/2020 18:09, Reef Turner wrote:
We would prefer users download NVDA from our site, it helps us understand
the uptake of a new version (through download stats), and reminds users to
consider donating (which makes it possible to keep providing NVDA).
Another concern is the longevity of the links, though we have no plans to
change the way NVDA is stored, we can't guarantee this will always be
true.

That said, we wouldn't want a lack of translation to be the reason someone
is unable to use the latest version of NVDA.

We suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get statistics
appropriately.
I'm not sure at which point the stats are collected. You are right,
theoretically we could count the stats when the file is accessed, in
practice I have a feeling we don’t do that. I think it is tied to the
download button on the download page. Either way, we get a slightly
different statistic based on checks for updates. In my opinion this is
more useful, it gives a better indication of daily active users.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia
Ruiz
Sent: Wednesday, 29 July 2020 4:27 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Question for NV Access staff: Can we share the
direct link to download NVDA?

Hello, I think this is possible, but do you agree with this practice,
considering that the NV Access download page is not translated and the
donation system is just in English?
We have shared the direct link on the spanish list for NVDA created by me
at groups.io, but we'd like to be sure that you agree about this practice.
We suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get statistics
appropriately.
I haven't posted the direct link to stable version on the website
associated with the mailing list in case you prefer we don't share it.
Can you clarify this?
On the website we say, in Spanish: To download NVDA, go to NV Access
website and then press the DOWNLOAd button, but this maybe tricky:
https://nvdaes.github.io/nvda-2020-2/

Thanks






--


Sean

* Email: seantolstoyevski@...
<mailto:seantolstoyevski@...>
* GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

👨‍🦯 I’m programmer. I coding often Python, sometimes Go and rarely C++.





Re: Question for NV Access staff: Can we share the direct link to download NVDA?

Noelia Ruiz
 

I think that it would be useful if the website was translated, maybe
with a warning to clarify that translations are not official but just
informative. Communnities have websites, blogs or social network to
inform users anyway, so I don't know how this can be put all together.
For instance, the add-ons website is localized in several languages,
but communities host add-ons in their own websites in several
languages. So, the concern is: if the translation provided in NV
Access servers is not official, what's the additional value of hosting
a translation on their website? It would be useful if some kind of
endorsement could be provided for the translations hosted in their
website, but I don't know if this is or not possible or what would be
required.
NV Access announced that they would work in the translation system for
NVDA and add-ons. Maybe a chance to take a look on this again?
Here is a closed issue for this:
https://github.com/nvaccess/nvda/issues/6392

2020-07-29 20:52 GMT+02:00, Sean <s.tolstoyevski@...>:

I think it is a deficiency that NVDA's official site only serves in
English.

If WordPress translation templates are shared, I would be happy to
translate the site into Turkish.
Very good at Wordpress i18n.

In addition: it is difficult to generate an analysis with just the
download button click counter. This is a simple thing.
Instead, a token-based download system may be needed.

On 29/07/2020 18:09, Reef Turner wrote:
We would prefer users download NVDA from our site, it helps us understand
the uptake of a new version (through download stats), and reminds users to
consider donating (which makes it possible to keep providing NVDA).
Another concern is the longevity of the links, though we have no plans to
change the way NVDA is stored, we can't guarantee this will always be
true.

That said, we wouldn't want a lack of translation to be the reason someone
is unable to use the latest version of NVDA.

We suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get statistics
appropriately.
I'm not sure at which point the stats are collected. You are right,
theoretically we could count the stats when the file is accessed, in
practice I have a feeling we don’t do that. I think it is tied to the
download button on the download page. Either way, we get a slightly
different statistic based on checks for updates. In my opinion this is
more useful, it gives a better indication of daily active users.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia
Ruiz
Sent: Wednesday, 29 July 2020 4:27 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Question for NV Access staff: Can we share the
direct link to download NVDA?

Hello, I think this is possible, but do you agree with this practice,
considering that the NV Access download page is not translated and the
donation system is just in English?
We have shared the direct link on the spanish list for NVDA created by me
at groups.io, but we'd like to be sure that you agree about this practice.
We suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get statistics
appropriately.
I haven't posted the direct link to stable version on the website
associated with the mailing list in case you prefer we don't share it.
Can you clarify this?
On the website we say, in Spanish: To download NVDA, go to NV Access
website and then press the DOWNLOAd button, but this maybe tricky:
https://nvdaes.github.io/nvda-2020-2/

Thanks






--


Sean

* Email: seantolstoyevski@...
<mailto:seantolstoyevski@...>
* GitHub: SeanTolstoyevski <https://github.com/SeanTolstoyevski/>

👨‍🦯 I’m programmer. I coding often Python, sometimes Go and rarely C++.





Re: Question for NV Access staff: Can we share the direct link to download NVDA?

Sean
 

I think it is a deficiency that NVDA's official site only serves in English.

If WordPress translation templates are shared, I would be happy to translate the site into Turkish.
Very good at Wordpress i18n.

In addition: it is difficult to generate an analysis with just the download button click counter. This is a simple thing.
Instead, a token-based download system may be needed.

On 29/07/2020 18:09, Reef Turner wrote:
We would prefer users download NVDA from our site, it helps us understand the uptake of a new version (through download stats), and reminds users to consider donating (which makes it possible to keep providing NVDA). 
Another concern is the longevity of the links, though we have no plans to change the way NVDA is stored, we can't guarantee this will always be true.

That said, we wouldn't want a lack of translation to be the reason someone is unable to use the latest version of NVDA.

We suppose that if we don't host the launcher on an external website or service, if someone downloads NVDA from this link you can get statistics appropriately.
I'm not sure at which point the stats are collected. You are right, theoretically we could count the stats when the file is accessed, in practice I have a feeling we don’t do that. I think it is tied to the download button on the download page. Either way, we get a slightly different statistic based on checks for updates. In my opinion this is more useful, it gives a better indication of daily active users.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia Ruiz
Sent: Wednesday, 29 July 2020 4:27 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Question for NV Access staff: Can we share the direct link to download NVDA?

Hello, I think this is possible, but do you agree with this practice, considering that the NV Access download page is not translated and the donation system is just in English?
We have shared the direct link on the spanish list for NVDA created by me at groups.io, but we'd like to be sure that you agree about this practice. We suppose that if we don't host the launcher on an external website or service, if someone downloads NVDA from this link you can get statistics appropriately.
I haven't posted the direct link to stable version on the website associated with the mailing list in case you prefer we don't share it.
Can you clarify this?
On the website we say, in Spanish: To download NVDA, go to NV Access website and then press the DOWNLOAd button, but this maybe tricky:
https://nvdaes.github.io/nvda-2020-2/

Thanks







--

Sean

👨‍🦯 I’m programmer. I coding often Python, sometimes Go and rarely C++.


Re: Question for NV Access staff: Can we share the direct link to download NVDA?

Noelia Ruiz
 

OK, then, in case, we won't share the direct download link on the
website and will share a link to this thread so people checks for
updates of NVDA or use the download button.
Thanks

2020-07-29 17:09 GMT+02:00, Reef Turner <reef@...>:

We would prefer users download NVDA from our site, it helps us understand
the uptake of a new version (through download stats), and reminds users to
consider donating (which makes it possible to keep providing NVDA).
Another concern is the longevity of the links, though we have no plans to
change the way NVDA is stored, we can't guarantee this will always be true.

That said, we wouldn't want a lack of translation to be the reason someone
is unable to use the latest version of NVDA.

We suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get statistics
appropriately.
I'm not sure at which point the stats are collected. You are right,
theoretically we could count the stats when the file is accessed, in
practice I have a feeling we don’t do that. I think it is tied to the
download button on the download page. Either way, we get a slightly
different statistic based on checks for updates. In my opinion this is more
useful, it gives a better indication of daily active users.

-----Original Message-----
From: nvda-devel@groups.io <nvda-devel@groups.io> On Behalf Of Noelia Ruiz
Sent: Wednesday, 29 July 2020 4:27 PM
To: nvda-devel@groups.io
Subject: [nvda-devel] Question for NV Access staff: Can we share the direct
link to download NVDA?

Hello, I think this is possible, but do you agree with this practice,
considering that the NV Access download page is not translated and the
donation system is just in English?
We have shared the direct link on the spanish list for NVDA created by me at
groups.io, but we'd like to be sure that you agree about this practice. We
suppose that if we don't host the launcher on an external website or
service, if someone downloads NVDA from this link you can get statistics
appropriately.
I haven't posted the direct link to stable version on the website associated
with the mailing list in case you prefer we don't share it.
Can you clarify this?
On the website we say, in Spanish: To download NVDA, go to NV Access website
and then press the DOWNLOAd button, but this maybe tricky:
https://nvdaes.github.io/nvda-2020-2/

Thanks