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

Make mouse tracking use display model, when other methods of text retrieval fail #3929

Open
nvaccessAuto opened this issue Feb 26, 2014 · 5 comments

Comments

@nvaccessAuto
Copy link

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?

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2014-02-26 11:39
From what I can see from the code, we're already doing this. It certainly works for me, for example, in the Excel cell editing field. It'd be good if you can provide specific examples of where this isn't working in freely available applications.

@nvaccessAuto
Copy link
Author

Comment 2 by k_kolev1985 on 2014-02-26 11:56
Well, in applications like Balabolka, Cobian Backup, KMPlayer (all free). In their settings windows, there are static text controls, witch describe some of the functions/controls in there. Those static text controls (if I'm calling them right) are not read by NVDA's mouse tracking. For example, in Balabolka, in menu Options -> Text Import -> Text Import Settings dialog, in the "Text Extracting" tab, on the right of the dialog, there are 2 paragraphs of text, witch NVDA does not read via its mouse tracking, but it does read via its screen review.

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.

@LeonarddeR
Copy link
Collaborator

I also recall that mouse tracking uses the display model just fine. @k-kolev1985, is this still an issue for you?

@k-kolev1985
Copy link

@LeonarddeR Yes, this is still an issue for me.

@Adriani90
Copy link
Collaborator

@LeonarddeR If I am not wrong you have been working on a possibly related PR regarding displaymode. Do you have any updates?

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