TranslateScreenPoint returns wrong values on Win 10 1607

PDF-XChange Viewer SDK for Developer's
(ActiveX and Simple DLL Versions)

Moderators: TrackerSupp-Daniel, Tracker Support, Vasyl-Tracker Dev Team, Sean - Tracker, Chris - Tracker Supp, Tracker Supp-Stefan, Ivan - Tracker Software

Post Reply
Posts: 52
Joined: Tue Dec 28, 2004 9:49 am

TranslateScreenPoint returns wrong values on Win 10 1607

Post by prosozial_schmitt » Fri Aug 12, 2016 12:44 pm

edit 2016-08-30

After debugging and testing with different Monitor/DPI constellations:
It seems, that this is not a problem of PdxChange-Viewer TranslateScreenPoint.
Windows 10 delivers in some cases/constellations negative ScreenPoint-positions. This wasn't expected by me and leads to an error. I can change my code to get around the problem.

Sorry and greetings


after upgrading to windows 10 Update 1607 the function TranslateScreenPoint seems to return wrong values.

Before upgrading, the function returns a correct value on screen dpi setting 100 and 200 (Windows option for text-scaling on hight-DPI monitors). The translated point matches with the pdf-page shown.

After upgrading to Windows 10 Update 1607, the function only returns a correct value on dpi setting 100.
On screen dpi setting 200 TranslateScreenPoint delivers a wrong value. The origin of the point is shifted to the right and to the bottom.

I've verified this on other systems without and with Windows 10 1607 Upgrade.

Is this a known problem?
Can I use an alternative function to get a correct pagepoint from screenpoint?


User avatar
Paul - Tracker Supp
Site Admin
Posts: 5016
Joined: Wed Mar 25, 2009 10:37 pm
Location: Chemainus, Canada

Re: TranslateScreenPoint returns wrong values on Win 10 1607

Post by Paul - Tracker Supp » Wed Aug 31, 2016 9:18 pm

If posting files to this forum - you must archive the files to a ZIP, RAR or 7z file or they will not be uploaded - thank you.

Best regards

Paul O'Rorke
Tracker Support North America

Post Reply