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

NVDA is preventing text expander software from working #5144

Closed
nvaccessAuto opened this issue Jun 5, 2015 · 4 comments
Closed

NVDA is preventing text expander software from working #5144

nvaccessAuto opened this issue Jun 5, 2015 · 4 comments

Comments

@nvaccessAuto
Copy link

Reported by gmhtml on 2015-06-05 20:12
I have now tried working with phrase express, quick fox, pylot. These are text expanders for transcription projects using abbreviated text which then expands into words or sentences. Each time the text is expanded, it becomes truncated, or fails to expand when using NVDA correctly. At times the expantion is cut in the middle rendering only some letters from the word. This is crucial software used for medical transcription, translators, dedicated typing jobs, and badly needed to be usable.
Blocked by #4499

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2015-06-06 09:16
Is this the same issue as #4499? If so, please see the workaround in ticket:4499#comment:3.

@nvaccessAuto
Copy link
Author

Comment 2 by gmhtml (in reply to comment 1) on 2015-06-20 22:44
Replying to jteh:

Is this the same issue as #4499? If so, please see the workaround in ticket:4499#comment:3.

Thank you, yes it is, and the problem is now solved. However the name of the control to change this behavior has now changed in later versions of NVDA from intercept keys from other applications, to handle keys from other applications which caused some confusion.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2015-06-22 05:16
Okay. Closing as a duplicate of #4499.
Changes:
Added labels: duplicate
State: closed

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2015-07-10 04:31
The fix for #4499 is now in master. The reporter confirmed that it fixed the issue. However, your comment suggests that your issue isn't fixed. If you can definitely confirm that this is still broken for you after waiting a few days and testing a master snapshot, please reopen this ticket and we'll discuss further.

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

1 participant