Zoom rectangle misplaced at 150% DPI

[schiplonkar]

Hello,

We are using Steema.TeeChart.Net (4.2019.5.15) version in windows forms application. The zoom rectangle on the chart is misplaced when the windows display setting is 125 or 150%.

If you want to reproduce this issue then just create a simple project with T CHart control on the form. Change the display settings for the monitor to use 150% and run the application. Use the mouse to select a region on the chart to zoom. You can see the dashed rectangle is not where the mouse pointer is used to drag the rectangle.

I believe there is an open bug # 814 with the same issue. Please let me know if there is a fix or a workaround for this issue.

Thanks

Sanjay

[Christopher]

Hello Sanjay,

In the issue report here:
http://bugs.teechart.net/show_bug.cgi?id=814

In my reply there is a link to a StackOverflow question on the same theme, and on StackOverflow you can see that there is relatively recent possible answer to the problem here - have you tried this technique in your application?

[schiplonkar]

Hello,

I have tried the SetProcessDPIAware solution. That did not seem to have any effect. The rectangle dotted line does not appear close to the actual mouse pointer. Please let me know if you have another workaround.

Thanks

Sanjay

[Christopher]

Hello Sanjay,

please be aware that this is not a TeeChart issue, but is an issue with application settings for DPI. Another possibility is to use the dpiAware manifest settings about which you can read here and here.

[Mikej]

Was wondering if this ever got resolved. I am seeing a similar issue. Our main application that consumes the TeeChart control is DPI Aware. We had to do many things to fix issues when the Display settings were set to > 100%.

However in TeeChart, I am seeing the Zoom Rectangle actually showing up on my 2nd monitor which is external to my laptop screen where the TeeChart is located.

While I am using TeeChart 3.5, it seems to be a the same issue you are seeing. Was hoping to hear if this issue was resolved.

[Christopher]

While I am using TeeChart 3.5, it seems to be a the same issue you are seeing. Was hoping to hear if this issue was resolved.

As I explained in my last message, this is not a TeeChart issue (an issue pertaining to an app component), but is an issue of the configuration of the app itself.