Skip to content


Using The NVDA OCR plugg-in! #2331

nvaccessAuto opened this Issue · 8 comments

2 participants


Reported by Brendon22 on 2012-05-13 12:41
Hi, When using The OCR Plugg-in and After doing an OCR of The Screen. And trying to read it NVDA will just admit The NVDA Errar Sound? Using NVDA Version 2012.2beta1.


Comment 1 by MHameed on 2012-05-13 12:59
This is not enough information to find the cause of the problem, can you please provide a log.


Attachment NVDA Log.txt added by Brendon22 on 2012-05-16 00:37
My NVDA Log from 16/05/12


Comment 2 by jteh on 2012-06-08 06:56
You need to use the NVDA review cursor to read the OCR text, not the system caret. This is by design; the text isn't actually available using the caret.

That said, errors when you try to move the caret still aren't ideal. Ideally, the caret should just work as normal, though I'm not sure how to implement this.


Comment 3 by Brendon22 on 2012-06-08 07:08
Thanks for that, and I agree with you about the errars.


Comment 4 by Brendon22 on 2012-08-21 05:33
NVDA is still doing this.

  1. Open up a window wich I know has a picture in it that has text in it.

  2. Run OCR with NVDA plus R.

  3. Try and use your aro keys to read the OCRED text. NVdA gives me the following errar:

ERROR - eventHandler.executeEvent (15:26:24):
error executing event: caret on with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyc", line 136, in executeEvent
File "eventHandler.pyc", line 84, in init
File "eventHandler.pyc", line 91, in next
File "NVDAObjects\IAccessible__init__.pyc", line 1244, in event_caret
File "NVDAObjects\window\edit.pyc", line 791, in event_caret
File "C:\Users\Brendon Donohue\AppData\Roaming\nvda\addons\ocr\globalPlugins\", line 207, in
File "C:\Users\Brendon Donohue\AppData\Roaming\nvda\addons\ocr\globalPlugins\", line 96, in init
File "textInfos\offsets.pyc", line 275, in init
File "textInfos\offsets.pyc", line 165, in _getSelectionOffsets
NotImplementedError, Log set to input.


Comment 5 by jteh on 2012-08-21 05:59
As noted in comment:2, you aren't meant to be able to read the OCRed text using the arrow keys.


Comment 6 by Brendon22 on 2012-08-21 06:46
Oh Yes, sorry!


Comment 7 by Brendon22 on 2014-05-29 10:52

These issues haven't been resolved yet. Any progress on this?

@jcsteh jcsteh was assigned by nvaccessAuto
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.