The issue is reproducible when the DPI is changed at runtime(new feature introduced with Windows 10) and therefore the application is not notified for the change. In order the application to be aware of the change the user have to logout and sign in (or the application should be DPI aware).
This can be observed only when AllowTransparance is set to false.
When creating a Word plug-in project for example, after showing a RadWindow instance moving that window by dragging it causes NullReferenceException. Available in LIB version 2016.1.222, it will be also available in the 2016 Q2 Release.
If RadWindow has its Width set to a value greater that 50% of the screen and that window is snapped to the left or right, performing minimize and then restore leads to incorrect normal size . Available in LIB version 2015.3.1123, it will be also available in the 2016 Q1 release.
This happens when RadWindowInteropHelper.AllowTransparency is set to False and RadWindow is implemented as UserControl. The Window need to be maximized firstly on the main screen and then on the secondary in order for issue to be reproduced. The issue also affects the ToolWindow that RadDocking uses for its floating Pane. In order to reproduce the problem, the primary monitor needs to have its DPI higher than the secondary one.
It happens when IsRestrictedWhenMaximized set to true.
1) Open WPF Demos and maximize it 2) Open "Alert, Prompt and Confirm" sample 3) Click "Confirm" 4) Minimize all windows (for example, by using Win+D) 5) Switch to WPF Demos again 6) Now you can't do anithing with the window, even close it. You can use task manager to close it.
Setting the Owner property to null in order to detach the minimize behavior of linked RadWindow instance to its owner does not take effect unless the RadWindow instance is closed and reopened. Available with the R3 2016 SP1 release.
Available in LIB version 2015.3.1130, it will be also available in the 2016 Q1 Release.
Available in the 2015 Q3 Release.
If you have set SizeToContent of RadWindow to true and you use one of the following options, SizeToContent will not work. - UseLayoutRounding = true - TextOptions.SetTextFormattingMode(dialog, TextFormattingMode.Display); Available in the 2015 Q3 Release.
Place Expander as content in RadWindow. Once expanded, the SizeToContent feature stops working as expected. Available in the 2015 Q3 Release.
The thrown error is that the element that should be set as FocusedElement cannot be found. Available in LIB version 2016.2.606, it will be also available in the 2016 R2 SP1 release.
Moving a window fast on low performance machine or between two monitors causes incorrect offset to be applied to the mouse cursor
In WPF browser application it is possible to move the focus of a focused TextBox control inside the RadWindow to the parent page with Shift+Tab keyboard combination