Completed
Last Updated: 13 Dec 2019 13:15 by ADMIN
LindenauAtSOG
Created on: 10 Oct 2019 08:57
Category: UI for WPF
Type: Bug Report
3
Dragging maximized Window allways maxes on primary screen

Requirements:

- Multiple screen RDP-Session with option "Show windowcontents while dragging" turned off.

- RadTabbedwindow with AllowTransparency = false (might not be necessary)

 

When dragging a maximized TabbedWindow to a different screen into maximized mode, it is allways maximized on the primary screen.
Dragging it on the target screen so that it is not maximized and then clicking maximize works.

The issue only appears when the mentiond setting in the RDP-Session is turned off.

13 comments
ADMIN
Dilyan Traykov
Posted on: 13 Dec 2019 13:08

Hello,

I'm happy to hear that the issue is resolved in the 1909 Windows 10 build.

I will proceed with closing this bug report but if you do come across any other issues, do not hesitate to contact us again.

Regards,
Dilyan Traykov
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
LindenauAtSOG
Posted on: 12 Dec 2019 11:44
I managed to test it on a 1909 machine now and the bug could not be reproduced.
Thats good enough for me.
Thank you for your help.
ADMIN
Dilyan Traykov
Posted on: 04 Dec 2019 12:24

Hello,

This is indeed unfortunate.

Can you please clarify whether both issues remain - the window maximizes on the wrong screen and there is the gap reserved for the taskbar or if it's only one of the two things?

As I'm still unable to replicate this at my end, could you please try testing this on a Windows 10 1809 machine and let me know if you still observe the undesired behavior?

Thank you in advance for your cooperation on the matter.

Regards,
Dilyan Traykov
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
LindenauAtSOG
Posted on: 28 Nov 2019 06:38
Hello,

i just tested it with 2019.3.1125.45 and sadly, the bug is still there.

Our IT hasnt managed to update Windows on the servers we are running yet, so i cannont confirm if its related to our "old version" of Windows Server 2016. 
ADMIN
Dilyan Traykov
Posted on: 27 Nov 2019 16:32

Hello,

I'm just checking in to see whether you managed to test our internal build and whether the issue is resolved with it. If that is the case, please let us know so that we can close this bug report.

Thank you in advance for your feedback.

Regards,
Dilyan Traykov
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
ADMIN
Dilyan Traykov
Posted on: 14 Nov 2019 17:35

Hello,

As you might have already seen, the fix to the issue you referred to will be available with our next internal build on the 18th of November. Please let us know once you manage to test it out.

Regards,
Dilyan Traykov
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
LindenauAtSOG
Posted on: 14 Nov 2019 12:58

This might be the same issue 

https://feedback.telerik.com/wpf/1441150-window-doesn-t-resize-correctly-when-dragged-from-primary-monitor-and-docked-on-the-top-of-the-screen-of-a-secondary-monitor-which-has-no-taskbar-and-dragging-animation-is-disabled

We will try the new Version once it is released.
ADMIN
Dilyan Traykov
Posted on: 29 Oct 2019 09:36

Hello,

Thank you very much for the additional details.

The video you provided gives us a pretty good understanding of the issue and I do not believe a remote session would shed more light on its cause.

I want to state that the build of Windows I tested this on is 1809 and since you've tracked this down to the framework's UpdateDimensionsToRestoreBounds I assume there is some chance that this issue has been fixed with this version of Windows 10. Would you find it possible to test the behavior with this Windows build?

Regards,
Dilyan Traykov
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
LindenauAtSOG
Posted on: 22 Oct 2019 10:12

Latest internal build  (2019.3.1014.45) didnt help, sadly.
We are using 2019.3.917.465 in production where the issue occurs.

Winver shows Microsoft Windows Server 2016
Version 1607 (Build 14393.3025)

I also fired up an old virtual Windows 10 Machine with following specs that the bug can be observed on:

Windows 10
Version 1803 (Build 17134.829)

 


What i did to further narrow it down was enabling debugging of .net-Framework and i can atleast identify the part that makes the Window "move" back to the wrong window.
In Window.cs there is a Method called UpdateDimensionsToRestoreBounds, see
https://referencesource.microsoft.com/#PresentationFramework/src/Framework/System/Windows/Window.cs,4884

When i set a breakpoint before it enters that method, the Window is correctly maximized. After it goes through there, the bug occurs.

So something prevents the Window from updating its RestoreBounds correctly. Sadly i can't digg deeper.

We will live with that bug for now, since there is the workaaounr of enabled mentiond rdp option.
If you want to further investigate, we could do a TeamViewer-Session so you can debug live on my machine.

ADMIN
Dilyan Traykov
Posted on: 21 Oct 2019 14:37

Hello again,

Thank you for the clarifications and the provided image and project.

I ran the same project with the same settings you've specified, however, maximizing the window works correctly at my end once more. I've attached another recording which demonstrates the observed result.

Can you please specify the exact build version of Windows on both machines as well as the exact version of the Telerik UI for WPF suite you're using? Would you also find it possible to try using the latest internal build and see if you still experience the issue?

I will be looking forward to your reply.

Regards,
Dilyan Traykov
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Attached Files:
LindenauAtSOG
Posted on: 16 Oct 2019 13:53

Thank you for your investigation.

I attached a recording of how I am doing it.

Im not doing anything much different from you.
You can see the bug in action there. Also notice the incorrect clipping of the taskbar.

Let me try if i can provide more details in order to reproduce this.
I attached the solution i am using to reproduce this issue.

Also:
- Framework 4.8
- Binaries.NoXaml
- Fluent Theme
- Primary screen left, secondary right
- Taskbar only on left side of primary screen
- 1920 x 1200 @100% on both screens

Maybe its something wrong with how i included references of the merged dictionaries?

ADMIN
Dilyan Traykov
Posted on: 16 Oct 2019 12:22

Hi LindenauAtSOG,

I tried replicating the behavior you described at my end with the settings you specified, however, maximizing the window seems to work as expected on my machine.

I've prepared a short recording of the behavior I observe. Could you please have a look and let me know if I'm missing something of importance?

Thank you in advance for your cooperation on the matter.

Regards,
Dilyan Traykov
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Attached Files:
LindenauAtSOG
Posted on: 10 Oct 2019 13:33
The description is not accurate, my appologies.

The issue orcurs when the "source" is not the primary monitor.

Also then there is another clippingissue with the taskbar, similiar to the other issue i recently reported.