Pages.ScreenX / Pages.ScreenY and Windows 10 1607
Posted: Mon Sep 05, 2016 9:00 am
Hello,
it seems, that after Windows 10 Update 1607 the values of Pages.ScreenX / Pages.ScreenY have changed on high textscaling-settings. (see screenshots in attachment)
I have set the text-scaling of my monitor to 200% (Microsoft Surface 4, high-dpi). So I have a scaling-factor of 2.
Before Windows 10 Update 1607, Pages.ScreenX / Pages.ScreenY values correspond to the screen-position of the control (all panes are hidden).
After Windows 10 Update 1607, Pages.ScreenX / Pages.ScreenY value don't correspond to the screen-position (tested again on a Surface 4, high-dpi, text-scaling 200%). They have doubled their value (seems to be position * scaling-factor, tested also with other scalings - same behaviour).
You can verify this with the code in the attachment. Copy it into the main-form of your sample-application and bind it to a button. After loading a pdf, just see the values on a pc with 200% textscaling with and without Update 1607.
I believe, that this behaviour affects also to the function TranslateScreenPoint.
All tested with PDF-Viewer 2.5.317.1.
What is going wrong? What can I change?
I don't want to code OS-dependend...
Greetings
Hans-Peter
it seems, that after Windows 10 Update 1607 the values of Pages.ScreenX / Pages.ScreenY have changed on high textscaling-settings. (see screenshots in attachment)
I have set the text-scaling of my monitor to 200% (Microsoft Surface 4, high-dpi). So I have a scaling-factor of 2.
Before Windows 10 Update 1607, Pages.ScreenX / Pages.ScreenY values correspond to the screen-position of the control (all panes are hidden).
After Windows 10 Update 1607, Pages.ScreenX / Pages.ScreenY value don't correspond to the screen-position (tested again on a Surface 4, high-dpi, text-scaling 200%). They have doubled their value (seems to be position * scaling-factor, tested also with other scalings - same behaviour).
You can verify this with the code in the attachment. Copy it into the main-form of your sample-application and bind it to a button. After loading a pdf, just see the values on a pc with 200% textscaling with and without Update 1607.
I believe, that this behaviour affects also to the function TranslateScreenPoint.
All tested with PDF-Viewer 2.5.317.1.
What is going wrong? What can I change?
I don't want to code OS-dependend...
Greetings
Hans-Peter