1. Home
  2. Forum
  3. WPF
  4. Moving window with ResizeMode = NoResize between monitors with different resolutions gives wrong results.

Moving window with ResizeMode = NoResize between monitors with different resolutions gives wrong results.

Good Afternoon,

I am using a ChromelessWindow with the MaterialDark theme and with ReseizeMode set to NoResize and I have the following monitors:

1) 1920x1080, scale: 125%
2) 1920x1200, scale 100%

If I drag it from monitor 1 to monitor 2, I get the following results:

Window on monitor 1:


Window on monitor 2:


This doesn't happen if ResizeMode is set to its default value.

If I drag the window back to monitor 1, the window is normal again.

Can you help me? Is this a bug?

Thanks in advance,
Luca


8 Replies
VR Vijayalakshmi Roopkumar Syncfusion Team September 7, 2020 09:58 AM UTC

Hi Luca, 
 
Thank you for contacting Syncfusion Support. 
 
We have checked the reported query and analyzed it by using our simple sample.We could able to see that combobox dropdown has been located properly at both monitors with the reported resolution respectively. Kindly find the sample which we have tried to reproduce the issue from following : 
 
 
So we would like to confirm the following details to know about exact replication scenarion 
 
  1. Your display settings as shown in below screenshot.
 
         
 
  1. Also how you placing the secondary and primary monitors.
 
  1. Your currently using syncfusion product version details.
 
 
Please provide the following details and also check with our sample whether it is reproduces the issue at your end. If not, kindly share us the simple sample, it would be helpful for us to analyze on this case better at our end. 
 
Please let us know if you have any other concerns. 
 
Regards, 
Vijayalakshmi VR 


LD Luca De Marco September 9, 2020 07:37 AM UTC

Hello,

1) Yes, the first monitor has the settings in the screenshot, while the second is a 1920x1200 and the size of text is 100%.
2) The primary monitor is the 1920x1080 one and the second, placed on the right of the first one is the 1920x1200 one.
3) I am using version 18.2.0.56 and I am developing using .NET Core 3.1.

Your sample works correctly. I'll try to create a stripped down version of my project to attach here to show my code.

In the meantime, thank you for your quick response!

Luca

LD Luca De Marco September 9, 2020 08:14 AM UTC

Hi,

I was able to strip it down quickly,

so I'll attach it here.

Thank you in advance,

Luca

Attachment: DemaDMS_d26af99f.7z

VR Vijayalakshmi Roopkumar Syncfusion Team September 10, 2020 10:26 AM UTC

Hi Luca, 
 
Thank you for your update. 
 
We have checked the reported behavior with ChromelessWindow and we were able to reproduce it. We have logged a defect report on this and the patch for the fix is estimated to be available on 24th Sep, 2020. 
You can track the status of this defect using the following feedback link: 
 
 
Please let us know if you have any other concerns. 
 
Regards, 
Vijayalakshmi VR. 


VR Vijayalakshmi Roopkumar Syncfusion Team September 24, 2020 12:05 PM UTC

Hi Luca, 
 
Thank you for your patience. 
 
Due to some complexity in fixing the reported issue with ChromelessWindow, we need some more time to fix  it. We will fix and check in all possible cases and provide you the patch details by 28th Sep, 2020. 
 
We appreciate your patience until then. 
 
Regards, 
Vijayalakshmi VR 


LD Luca De Marco September 24, 2020 01:46 PM UTC

Thank you very much for your help!

Do I have to do something special or I will find it in the next weekly version of SyncFusion on NuGet?

Thanks in advance,
Luca

VR Vijayalakshmi Roopkumar Syncfusion Team September 25, 2020 06:24 AM UTC

Hi Luca

Thank you for your update.

As promised earlier, we would provide you the patch on 28th Sep, 2020. However, we will intimate you once it include in our upcoming weekly nuget release 2020.

Please let us know if you have any other concerns.

Regards,
Vijayalakshmi VR

VR Vijayalakshmi Roopkumar Syncfusion Team September 28, 2020 06:22 AM UTC

Hi Luca 
 
Thank you for your patience. 
 
On analyzing the reported behavior with ChromelessWindow, we could found that this case occurs on using the Window Type. As ChromelessWindow derived from the Window , we suspect it is the behavior of MS window. So, we have post this reported query to Visual studio community and Microsoft support team to resolve this behavior . You can find the below links for the same: 
 
 
 
We will update you once we receive prompt solution on this. 
 
Please let us know if you have any other concerns on this. 
 
Regards, 
Vijayalakshmi VR 


Loader.
Up arrow icon