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

Activating the routing key above the current position in a LibreOffice document generates a stacktrace #4694

Open
nvaccessAuto opened this issue Dec 15, 2014 · 4 comments

Comments

@nvaccessAuto
Copy link

Reported by bramd on 2014-12-15 00:24
Activating the braille routing key above the current cursor position in a LibreOffice document generates the following stacktrace:

Traceback (most recent call last):
File "scriptHandler.pyc", line 176, in executeScript
File "globalCommands.pyc", line 1266, in script_braille_routeTo
File "braille.pyc", line 1362, in routeTo
File "braille.pyc", line 1108, in routeTo
File "braille.pyc", line 835, in routeTo
File "textInfos__init__.pyc", line 444, in activate
AttributeError: 'CompoundDocument' object has no attribute 'isInForeground'

Using the routing keys to move the cursor works fine. Tested with LibreOffice 4.3.4.1.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-12-15 04:53
Out of interest, apart from not throwing an exception, what did you expect it to do?

@nvaccessAuto
Copy link
Author

Comment 2 by bramd (in reply to comment 1) on 2014-12-15 22:21
Replying to jteh:

Out of interest, apart from not throwing an exception, what did you expect it to do?

Ehm, well, nothing really. I accidentally pressed the routing button twice, got this traceback and reproduced it.

@LeonarddeR
Copy link
Collaborator

LeonarddeR commented Sep 16, 2017

cc @bramd

@bramd
Copy link
Contributor

bramd commented Sep 16, 2017

Still reproducible here on latest next. It seems we need to implement the isInForeground property for CompoundDocuments. However, I don't know how to determine if such an object is in the foreground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants