RadPivotGrid and PivotGridSpreadExport - Scaling problem on a 4K monitor.

[Bexel Consulting]

Dear Telerik Team,

We have a scaling problem on a 4K monitor when using RadPivotGrid and calling the RunExport method over the PivotGridSpreadExport instance.

We created the small solution in Visual Studio 2019 which is enough to successfully recreate the issue. Please note that during the development of the solution, the automatic scaling option in Visual Studio was off.

After starting the solution on a 4K monitor and calling the RunExport method over the PivotGridSpreadExport instance, the scaling was automatically performed over the whole solution (all forms and all their components were scaled, see the attached screenshots). At the moment of starting the solution, Scale and Layout option (under Display Settings on Windows) was set to 150% (Recommended). The same invalid result was when we set that option to 175%. Also, we tried to start the solution with every possible value for the AutoScaleMode property (Font, Dpi, None, Inherit) for all existing forms in the solution. The result was the same every time.
We think that the RunExport method makes a problem - the scaling is valid when we skip that call (see the attached screenshots), under the same conditions.

The mentioned solution with the required files can be found on the following link:

https://webshare.bexelconsulting.com/public/bexel/607-jenwspc47/Telerik%20-%20PivotGridSpreadExport.RunExport%20-%20Scaling%20Problem.zip

Could you please take a look at the solution and investigate the described issue?

Should you have any further questions about the described issue, feel free to contact us.

Thank you in advance for your help.

[Dess | Tech Support Engineer, Principal]

Hello, Veljo,

I would recommend you to have a look at the following KB article which seems to be exactly the case you are facing:

https://docs.telerik.com/devtools/winforms/knowledge-base/app-becomes-dpi-aware 

The PivotGridSpreadExport internally uses The Document Processing Libraries. Feel free to use one of the suggested solutions.

I hope this information helps. If you need any further assistance please don't hesitate to contact me. 

Regards,
Dess | Tech Support Engineer, Principal
Progress Telerik

[Bexel Consulting]

Dear Dess,

Thank you for your prompt answer.

We made our application DPI unaware, as you suggested in a KB article, and thus successfully solved the issue.

Best regards,