Comment 1 by jteh on 2014-03-18 01:09
If you're talking about desktop apps, if there isn't a number already, adding it would be too expensive, since we'd have to constantly walk through objects to calculate the number. Perhaps a specific example of where this would be useful would help.

Comment 2 by vgjh2005 (in reply to comment 1) on 2014-03-19 05:46
Replying to jteh:

If you're talking about desktop apps, if there isn't a number already, adding it would be too expensive, since we'd have to constantly walk through objects to calculate the number. Perhaps a specific example of where this would be useful would help.

For example, the interface have two listview that have no listview name.. Now, we will enter the listview to browse the list item. I think add a number of each listview here. Add the number in order for that controls have no description and do not know what it is. Such as two editBox in the gui. When we press the Tab key, we will heard Editbox and Editbox, Add a number for them. As long as span it one time when the window is loading.

I am a little unsure of whether I follow this ticket or not. It seems to me that this ticket is requesting a feature by which NVDA would be able to report the number of the instance of any given element present on the page already.
E.g. A webpage contains three check boxes. If the proposed feature request is implemented, then NVDA would report these as check box 1, check box 2, and check box 3.
@vgjh2005 Could you please inform if my interpretation of this ticket is correct? Regardless, @jcsteh has noted in #3988 (comment) that this may be expensive to do from a performance standpoint. It would be interesting to determine whether the performance regressions such a feature may potentially cause outweighs its usefulness or vice versa.

Closing as duplicate from the issues listed in #3988 (comment)
Thank you @ruifontes for compiling this list.