Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Constant errors when moving around files in Studio recorder #3199

Closed
nvaccessAuto opened this issue May 4, 2013 · 5 comments
Closed

Constant errors when moving around files in Studio recorder #3199

nvaccessAuto opened this issue May 4, 2013 · 5 comments
Assignees
@michaelDCurran
Labels
app-specific bug close/invalid component/display-model

Comments

@nvaccessAuto
Copy link

Reported by pitermach on 2013-05-04 16:00
Version master-9172,1b62fc7
STR:
-Download studio recorder from aph.org/tech, install it and then open any file. Then either use the arrow keys to move around it, or press space to play the file.
When ever the file position changes there is a edit box on the screen that gets updated, and when it does this comes up:
ERROR - eventHandler.executeEvent (17:45:33):
error executing event: caret on <NVDAObjects.Dynamic_IAccessibleDisplayModelEditableTextWindowNVDAObject object at 0x04B045F0> 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 1285, in event_caret
File "NVDAObjects__init__.pyc", line 868, in event_caret
File "NVDAObjects__init__.pyc", line 903, in makeTextInfo
File "displayModel.pyc", line 159, in init
File "textInfos\offsets.pyc", line 280, in init
File "displayModel.pyc", line 403, in _getCaretOffset
File "displayModel.pyc", line 375, in _findCaretOffsetFromLocation
LookupError
@nvaccessAuto
Copy link
Author

Comment 1 by mdcurran on 2013-05-04 16:10
Please try the next available master snapshot when it comes out. Its possible that master 70606ca may fix the bug. If not then I shall look into this one.

@nvaccessAuto
Copy link
Author

Comment 2 by pitermach on 2013-05-05 12:42
Tested with master-9178,8090f41, and the issue is still there.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2013-05-26 22:46
Is this issue still present? There have been a few fixes since comment:1 that may have affected it.

@bhavyashah
Copy link

Since the original author of this ticket is unfortunately now out-of-reach, he/she failed to respond to @jcsteh's request for a status update in #3199 (comment), and it is possible that both NVDA as well as Studio Recorder updates may have resolved this issue overtime, unless we receive any feedback confirming the reported errors, I suggest closing. @ehollig

@LeonarddeR
Copy link
Collaborator

Agreed. Closing as invalid as per above comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelDCurran michaelDCurran

Labels
app-specific bug close/invalid component/display-model
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@LeonarddeR @michaelDCurran @nvaccessAuto @bhavyashah @ehollig