Ability for NVDA to indicate spell error in real time.

[nvaccessAuto]

Reported by aleskis on 2012-01-03 09:01
An innovative functionality in comparaison with other screenreader should be to implement a specific sound to indicate spelling errors, in real time during the writting. By this way, the time for rereading could be largely reduced.

[nvaccessAuto]

Comment 1 by ateu on 2012-01-03 10:24
Yes!
This is really a great idea!
I don't know whether is difficulte to implementing, because i don't know python. But would be very nice.

[nvaccessAuto]

Comment 2 by jteh on 2012-01-03 11:14
We had this idea quite some time ago. Unfortunately, implementing it proved to be problematic due to inconsistency and limitations across different applications. However, we may perhaps investigate this again.

[nvaccessAuto]

Incubated in f73b354.

[nvaccessAuto]

Incubated in 7778f21.

[derekriemer]

Hi,
Could _reportErrorInPreviousWord be set to return a Boolean? I am tempted to write an addon that would use this function (monkey patch it) and if a spelling error was found, I would keep a note of it, so that I could give users a report of their spelling error statistics, and maybe even write a game to improve spelling in real time. For example, you could open a dialog, and it would tell you your percentage of words incorrect, the total number of spelling errors ever, the number in this session of NVDA, whether you have spelled more words correctly than normal, and play a tone when you have spelled more words incorrectly than average.
I totally understand if this is a resounding No!

[jcsteh]

The function actually does the reporting, not just the checking, so you couldn't just call it from your own event. How/from where were you planning on calling it?

[derekriemer]

If possible I was going to monkeypatch it, and see if it returned true,
I haven't studied this in detail yet. Is that not possible?
It would be like
def _reportErrorInPreviousWord(self):
if _reportErrorInPreviousWord _old(self):
bla
else
bla

then I would assign that function in place of the one in the NVDAObject.

On 4/5/2016 4:03 PM, James Teh wrote:

The function actually does the reporting, not just the checking, so you
couldn't just call it from your own event. How/from where were you
planning on calling it?

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#2024 (comment)

---

Derek Riemer

• Department of computer science, third year undergraduate student.
• Proud user of the NVDA screen reader.
• Open source enthusiast.
• Member of Bridge Cu
• Avid skiier.

Websites:
Honors portfolio http://derekriemer.com
Awesome little hand built weather app!
http://django.derekriemer.com/weather/

email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu
Phone: (303) 906-2194

[jcsteh]

Ug. I think I'd prefer not to provide for a hack like that. The correct solution would be to allow add-ons to register for notifications about this, but I don't want to deal with that in this issue. :)

[derekriemer]

I totally understand. It's kind of an ugly hack. I just thought I would check before I look at other possible solutions like hacking envy wave or whatnot.

Sent from my heavily encrypted iPhone.
Please disregard errors as this is a smaller device.

On Apr 5, 2016, at 16:40, James Teh notifications@github.com wrote:

Ug. I think I'd prefer not to provide for a hack like that. The correct
solution would be to allow add-ons to register for notifications about
this, but I don't want to deal with that in this issue. :)
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

[nvaccessAuto]

Incubated in af5c2bc.

[nvaccessAuto]

Incubated in 5720fc3.