DPI awareness with different monitor DPIs

[cjwere]

Hi,

Love the virtual treeview! Even more now I'm using it with "High DPI" on one monitor.

When I drag my running program across to the other monitor all my forms and fonts rescale, but the virtual treeviews do not. my application declares multi monitor DPI awareness. I breakpointed on tbasevirtualTree.changescale and it is getting triggered. I have toAutoChangeScale set on (just been through and set this on all my virtual treeviews)

starting on my high DPI screen (192DPI):

, then dragging to my nomal 96DPI screen:

Note the tabs and button and font within the body of the treeview rescale correctly, but the node spacing and the header size and font do not.

Thanks,
Chris Were

[joachimmarder]

Which version of Delphi and VirtualTreeView are you using?

[cjwere]

Sorry I thought last night i should have added this: Windows 10 pro, Delphi 10.1 Berlin (no service packs applied yet), and Virtual Treeview 6.4.1 I’ve just started adding the high DPI support to my application and its a bit of a battle especially trying to support monitors with 2 different DPIs, eg depending on which monitor is set to be my primary one, the window decorations and system dialogs, file open dialogs etc seem not to scale- they run at the DPI of the primary monitor. Everything inside my window's client areas seems happy (mostly) aside from the TVirtualstringviews- which are fine also so long as i don’t move the windows between monitors. Thanks, Chris

…

On 15/12/2016, at 3:10 AM, Joachim Marder ***@***.***> wrote: Which version of Delphi and VirtualTreeView are you using? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#677 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXa962iUXodcHNKdn6X12U_Em9XpydaWks5rH_jtgaJpZM4LMgPR>.

[joachimmarder]

So far, TBaseVirtualTree.AutoScale() only scaled up the property DefaultNodeHeight if the text would not fit into a line. I just added some code that also scales DefaultNodeHeight down if the form's dpi changes.

However, I cannot test this right now because I have connected only one monitor to my PC. Could you please set a breakpoint in TBaseVirtualTree.ChangeScale() and see if FHeader.ChangeScale() is called?

[cjwere]

OK Joachim, can i test it for you? PS just did a test the other way, primary monitor 96 DPI, started application there, dragged to 192DPI screen on notebook and they didn’t scale up either ( I am using theming as well if this is relevant, win10 in this example). Its seems to work (scaling up at least) when the primary monitor is the high-DPI one, and in this scenario (this morning at least!) on some but not all of my virtual treeviews when the primary is low dpi. May have to check the form design ppis as i have edited a few on the high DPI screen…urrrrgh. I probably need to sort out better what’s happening in my current setup before i can test it reliably for you… Chris

…

On 15/12/2016, at 8:26 AM, Joachim Marder ***@***.***> wrote: So far, TBaseVirtualTree.AutoScale() only scaled up the property DefaultNodeHeight if the text would not fit into a line. I just added some code that also scales DefaultNodeHeight down if the form's dpi chnages. However, I cannot test this right now because I have connected only one monitor to my PC. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#677 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXa962EQ3MJsZDpmg6h6Qv0tQMG-R-Wmks5rIELrgaJpZM4LMgPR>.

[cjwere]

PS, no all my dam files still have pixelsperinch set to 96. Weird...

…

On 15/12/2016, at 8:26 AM, Joachim Marder ***@***.***> wrote: So far, TBaseVirtualTree.AutoScale() only scaled up the property DefaultNodeHeight if the text would not fit into a line. I just added some code that also scales DefaultNodeHeight down if the form's dpi chnages. However, I cannot test this right now because I have connected only one monitor to my PC. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#677 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXa962EQ3MJsZDpmg6h6Qv0tQMG-R-Wmks5rIELrgaJpZM4LMgPR>.

[joachimmarder]

OK Joachim, can i test it for you?

Sure. Use the GitHub master branch to test, as it already contains one fix compared to V6.4.1. Set a breakpoint on TBaseVirtualTree.ChangeScale() and see what code is executed and why.

[cjwere]

Thx will have a look tomorrow.

…

On Thu, 15 Dec 2016, 20:40 Joachim Marder, ***@***.***> wrote: OK Joachim, can i test it for you? Sure. Use the GitHub master branch to test, as it already contains one fix compared to V6.4.1. Set a breakpoint on TBaseVirtualTree.ChangeScale() and see what code is executed and why. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#677 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXa967pktSRqNPsAkoBRQMUp99XnLiSFks5rIO7tgaJpZM4LMgPR> .

[joachimmarder]

will have a look tomorrow.

Any news on how the master branch worked for you?

[joachimmarder]

We should add a new event OnAutoScaled, that way one can easily adjust values that do not fit specific needs.

[cjwere]

Sorry Joachim was trying to get a release out. Will have a look today.

…

On Thu, 22 Dec 2016, 01:33 Joachim Marder, ***@***.***> wrote: We should add a new event OnAutoScaled, that way one can easily adjust values that do not fit specific needs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#677 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXa96zIqB9PCmnWqD6SRvXvYg7lrGBHeks5rKRyPgaJpZM4LMgPR> .

[joachimmarder]

Will have a look today.

Any news how the GitHub master works for you?