I use XamDockManager and have some DockPanels (left, right, and bottom of the content)..
The problem is when I try to resize panel (by using mouse drag on DockedPaneSplitter), it intermittently cancelled (do nothing).When it occurs and I check DockedPaneSplitter_DragCompleted event, the e.Canceled is true.
From the test, this problem only occurs when all these conditions are true:1. Monitor DPI is different between primary and second monitor (I change [Display > Scale and Layout] to 175% to reproduce this)2. Application is not on primary monitor (put application on second monitor)3. HwndHost is set as content in our DockManagerPanel
Additional info: I am using dual monitors and run the application on my second monitor in Windows 10.
Please let me know what can caused resizing panel to be canceled, and how can I prevent this to happen.
stack trace when this issue occurs.
Hello Edo Gasali,
Thank you for making a post to our forum.
I'm afraid to say that I am not sure whether or not I clearly understand what you mean by "3. HwndHost is set as content in our DockManagerPanel".
Could you give us an isolated, executable and reproducible sample which is made as simple as possible so that we can also see your issue on our side?
Somehow I can't attach file on this forum.So I put it here: https://gofile.io/?c=7B6OTO
Steps to reproduce:1. Use dual monitor2. Set different DPI on second monitor. example: [Display > Scale and Layout] to 175%3. Run application and move it to second monitor4. Try to resize pane on the right several times, sometimes it will be canceled
Thank you very much for providing the sample.
I downloaded it and could buid it on my side. I'll start the investigation with this sample.
This is a quick note to thank you. I'll let you know when there is any update about this matter.
We've been trying to reproduce your issue, but so far we haven't been able to if we exactly follow the steps to reproduce.
If you change the DPI, Windows warns you that some applications won't behave themselves expectedly, and if you want to avoid it, Windows requires you to restart applications or sign out and then sign in the Windows again.As long as we follow this requirement by Windows, the issue is not reproduced on our side.
Could you double-check whether the issue becomes not to be reproduced if you follow this requirement?