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 NVDA DPI aware #3758
Comments
Comment 3 by jteh on 2014-01-09 12:02
See also Writing DPI-Aware Desktop and Win32 Applications for an in-depth discussion of this high DPI stuff. |
Comment 4 by James Teh <jamie@... on 2014-01-16 03:05
Changes:
|
Comment 6 by James Teh <jamie@... on 2014-01-17 00:02
|
Comment 7 by jukesy1992 on 2014-01-28 15:48 |
Comment 8 by jteh on 2014-01-28 22:06 My guess is that the application isn't DPI aware, but I introduced code which should work around that for screen review and it does seem to work for me in some applications i tested. I'll need to investigate further. |
Comment 9 by jukesy1992 on 2014-01-29 15:38 |
Comment 10 by jteh on 2014-01-29 22:06 |
Comment 11 by jukesy1992 on 2014-01-30 17:17 |
Comment 12 by jteh on 2014-01-30 21:58 |
Comment 13 by jukesy1992 on 2014-02-05 12:08 |
Comment 14 by James Teh <jamie@... on 2014-02-11 03:28
Changes:
|
Comment 15 by jteh on 2014-02-11 03:32 |
Comment 16 by jteh (in reply to comment 13) on 2014-02-11 04:53
As far as we can tell, this seems to be a bug in Windows. If we can think of a reasonable solution, we'll implement it, but right now, we haven't come up with anything. I've created #3875 to address this. You should be able to access some of what you need using object navigation; e.g. the menus in Demul. |
Reported by jteh on 2014-01-08 06:36
Many newer screens have higher DPI than the traditional 96 DPI. If an application isn't DPI aware, Windows will virtualise and scale the application.
Currently, NVDA isn't DPI aware. Because of the virtualisation, most of the locations we use are scaled appropriately; e.g. Win32 functions. Unfortunately, this doesn't appear to be entirely accurate, so routing the mouse often routes to the wrong position despite the scaling, causing issues such as #3703. Also, apps with custom IAccessible* implementations don't have locations virtualised.
We need to:
One other issue is that there may be apps with custom IAccessible* implementations that are DPI unaware. That will be tricky to handle. My feeling is that we should cross that bridge when a specific case arises.
Blocked by #3782
Blocking #3703
The text was updated successfully, but these errors were encountered: