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
Make mouse tracking use display model, when other methods of text retrieval fail #3929
Comments
Comment 1 by jteh on 2014-02-26 11:39 |
Comment 2 by k_kolev1985 on 2014-02-26 11:56 Hmm, are we using display model for Excel cell editing field? If so, no wonder NVDA does not report text selections in there - text selection reporting via the display model is not supported at present in NVDA, if I remember correctly. |
I also recall that mouse tracking uses the display model just fine. @k-kolev1985, is this still an issue for you? |
@LeonarddeR Yes, this is still an issue for me. |
@LeonarddeR If I am not wrong you have been working on a possibly related PR regarding displaymode. Do you have any updates? |
Reported by k_kolev1985 on 2014-02-26 11:33
At present, mouse tracking can read text from most controls. From most, but not all. It can't read text from some places, from witch screen review (via the display model) can. So, I guess, that mouse tracking is not using display model to get the text (at least in those cases). Examples of such applications from witch NVDA can't read text via its mouse tracking are Delphi-based ones, and mostly - from their static text controls. Screen review can read text from those controls just fine. Can it be made so NVDA will read text from such places (controls) with its mouse tracking, as it now can do it via its screen review?
The text was updated successfully, but these errors were encountered: