[SOLVED]CXTPWindowPos and DPI |
Post Reply |
Author | ||
cpede
Senior Member Joined: 13 August 2004 Location: Denmark Status: Offline Points: 668 |
Post Options
Thanks(0)
Posted: 17 January 2017 at 3:00am |
|
Has anyone also seen a problem when using CXTPWindowPos when changing DPI?
When e.g. running 100% DPI and using:
and then when changing to 150% DPI and using:
Then I see that the dialog size is the same, but the content cannot fit since it is scaled to 150% DPI. Any good ideas to solve this problem generally? -cpede
|
||
Product: Xtreme ToolkitPro (24.0.0)
Platform: Windows 10 (x64) Language: Visual Studio 2017 (C++) |
||
cpede
Senior Member Joined: 13 August 2004 Location: Denmark Status: Offline Points: 668 |
Post Options
Thanks(0)
|
|
Still not solved in v19 ??.
-cpede
|
||
Product: Xtreme ToolkitPro (24.0.0)
Platform: Windows 10 (x64) Language: Visual Studio 2017 (C++) |
||
markr
Senior Member Joined: 01 August 2004 Status: Offline Points: 443 |
Post Options
Thanks(0)
|
|
> Any good ideas to solve this problem generally?
My approach has been to append a DPI indicator to the lookup key (e.g. "WindowPlacement" becomes "WindowPlacement_192" for 200% scaling). So then you can either just track separate layouts (can't imagine users are changing DPI settings very often) or re-calculate and overwrite when you detect a change.
|
||
cpede
Senior Member Joined: 13 August 2004 Location: Denmark Status: Offline Points: 668 |
Post Options
Thanks(0)
|
|
Thanks for the idea, I will use that. Actually you would be surprised how often this is reported as a problem.
By the way, now the CXTPWindowPos class can be handled, but what about the CXTPResizeDialog and CXTPResizePropertySheet using the CXTPResize class Load/SavePlacement, will they have the same problem? And are you handling these the same way? -cpede
|
||
Product: Xtreme ToolkitPro (24.0.0)
Platform: Windows 10 (x64) Language: Visual Studio 2017 (C++) |
||
agontarenko
Admin Group Joined: 25 March 2016 Status: Offline Points: 289 |
Post Options
Thanks(0)
|
|
Hello, I'm glad to inform you that the issue has been addressed and fixed. The fix will be available in 19.1 release. Regards, Artem Gontarenko
|
||
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |