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.
Milestone changed from 2009.2 to None
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.
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.
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.
Comment 6 by jteh on 2010-05-09 05:47
Clarifying summary: this is not a normal edit window.
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"