CustomWindow DPI issue in when connected to external monitor in WPF RRS feed

  • Question

  • I am developing the custom window in WPF application. But the combobox in that window doesn't shown properly in the required location when the DPI is 125 and above.

    Sample : customwindowdpiissue.zip

    Replication steps:

    1. Connect one external monitor with your laptop or PC

    2. Change the DPI setting of your laptop of PC to 125% or above and the external monitor DPI settings can be 100% or above.

    3. Run the attached sample and click the button in that window, it will opens the CustomWindow.

    4. Drag that CustomWindow to the secondary monitor and open the combobox drop down.

    Observed result:

    The popup is opened at incorrect location in that window as shown in above image.

    Expected result:

    The popup should be opened in correct location.


    • Edited by Kumaran619 Friday, September 25, 2020 1:27 PM
    • Moved by CoolDadTx Friday, September 25, 2020 5:54 PM WPF related
    Friday, September 25, 2020 1:25 PM

All replies

  • I didn't test you application, but it seems you want to program a per Monitor DPI aware WPF app.
    Did you do look at the example project? Per Monitor DPI
    Friday, September 25, 2020 5:52 PM
  • This forum is for C#-specific questions only. Please post questions related to WPF in the new Microsoft Q&A forums.

    Michael Taylor http://www.michaeltaylorp3.net

    Friday, September 25, 2020 5:54 PM
  • I have tested my WPF application with your Per Monitor DPI aware but it didn't work. Is there any other suggestions to solve this case. And also it is working fine when the primary monitor and external monitor having 100% scaling. When changing the scaling of external monitor to 125% or 150%, the issue has been reproduced.

    Thank you.

    Thursday, October 29, 2020 12:58 PM
  • Great development!
    Friday, November 6, 2020 2:28 PM
  • Hi,

    Any update on the reported issue?


    Visithra Vengatesan

    Friday, December 4, 2020 8:52 AM
  • Hi Team,

    Any update on the reported issue?



    Tuesday, December 22, 2020 6:55 AM