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

Support for visual studio 2008's code window #457

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 8 comments
Closed

Support for visual studio 2008's code window #457

nvaccessAuto opened this issue Jan 1, 2010 · 8 comments
Milestone

Comments

@nvaccessAuto
Copy link

Reported by oaron on 2009-11-05 10:33
NVDA is not able to read the text in Visual studio 2008's code window. Everything else works except for that. The edit field seems to be a normal textbox.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2009-11-05 10:54
This should not block the next release, but we'll take a fix if someone offers it.

What gives you the impression that this is a standard edit control? If it isn't working, it probably isn't. There are relatively few controls that can simply be fixed by treating them as standard edit controls. Saying that they work in commercial screen readers is not enough, as these screen readers use video interception techniques to access the caret and text.
Changes:
Milestone changed from 2009.2 to None

@nvaccessAuto
Copy link
Author

Comment 2 by aleksey_s on 2009-11-05 12:01
I've tried to remap that control to edit, richedit and such. No success. If you know how to get the caret position from that control, this will enable us to write a support for it, since it exposes content through msaa accValue.

@nvaccessAuto
Copy link
Author

Comment 3 by vtsaran on 2010-02-06 23:17
I don't think this is a standard edit field. This is one of those MS controls that are completely exposed through MSAA using accValue property. I believe that every line is represented as an MSAA object, so at least the line-by-line navigation/reading could be implemented.

@nvaccessAuto
Copy link
Author

Comment 4 by vtsaran on 2010-02-06 23:21
Alternatively, automation methods could be used to extract the content from that window. I can't say for sure, but there exists object model access in visual studio.

@nvaccessAuto
Copy link
Author

Comment 5 by mdcurran on 2010-02-07 00:14
Again, if someone wants to provide some code we'll take it. But when VS 2010 comes out, NVDA definitely will support the code editor in that version.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2010-05-09 05:47
Clarifying summary: this is not a normal edit window.
Changes:
Changed title from "Support for visual studio 2008's code window. It is a normal edit box." to "Support for visual studio 2008's code window"

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2010-06-01 05:17
Implemented thanks to Soronel Haetir in 0af1f76.
Changes:
State: closed

@nvaccessAuto
Copy link
Author

Comment 8 by jteh on 2010-06-01 05:18
Changes:
Milestone changed from None to 2010.2

@nvaccessAuto nvaccessAuto added this to the 2010.2 milestone Nov 10, 2015
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