Completed
Last Updated: 08 Feb 2016 16:33 by ADMIN
Completed
Last Updated: 12 Apr 2016 10:47 by ADMIN
When the attached TextOptions.TextFormattingMode="Display" property is set to the RadWindow the window stops auto resizing its size according to the size of its content.
Completed
Last Updated: 08 Aug 2016 13:32 by ADMIN
If a ContentControl is placed inside the control and the ResizeMode is set to NoResize the SizeToContent doesn't take effect.

As a workaround all you need to do is set the ResizeMode to NoResize in the Loaded event of the ContentControl.
Completed
Last Updated: 13 Jan 2016 15:00 by ADMIN
Currently the template of the dialogs should be customized:
http://www.telerik.com/community/code-library/wpf/window/how-to-modify-the-alert-dialog-icon.aspx

Available in the 2016 Q1 Release: Added an IconTemplate property that provides an easier way to change the predefined dialogs' exclamation/question mark images.
Completed
Last Updated: 01 Jul 2024 11:22 by ADMIN
Release 2024.2.701 (Preview)
In a scenario where a modal RadWindow is closed and it is opened via a separate thread, the Host property of the WindowWithNoChromeWindowHost class in the BringIntoFront method may be null, which raises an NRE exception.
Completed
Last Updated: 25 Oct 2016 14:04 by ADMIN
Completed
Last Updated: 22 Jan 2016 13:04 by ADMIN
Completed
Last Updated: 12 Oct 2015 06:13 by Wade
Available in the 2015 Q3 Release.
Completed
Last Updated: 05 Jul 2019 09:33 by ADMIN
Release LIB 2019.2.708 (7/8/2019)
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.
Completed
Last Updated: 13 Nov 2019 15:50 by ADMIN
Release LIB 2019.3.1118
The Window doesn't resize correctly when dragged from the primary monitor (with taskbar) and docked to the top of the screen of a secondary monitor (no taskbar) in order to maximize it and "Show window contents while dragging" Windows system setting is disabled.
Completed
Last Updated: 25 May 2015 14:02 by ADMIN
Completed
Last Updated: 26 Jun 2019 05:22 by ADMIN
Release LIB 2019.2.701 (7/1/2019)
The header buttons elements are not on the proper places when the window is on a monitor with different DPI. To reproduce this the DPI of the monitors should be different for example 125% (main) and 150% (secondary). Also, to reproduce this you will need to enable the DPI awareness of the application by setting the dpiAware and dpiAwareness settings in the app.manifest file.
Completed
Last Updated: 10 Aug 2015 09:47 by ADMIN
Maximizing RadWindow from the header button shows a window with the size of the content if SizeToContent = true. If you maximize with double click on header it is ok.
Completed
Last Updated: 16 Jul 2019 08:18 by ADMIN
Release LIB 2019.2.715 (7/15/2019)
Moving a window fast on low performance machine or between two monitors causes incorrect offset to be applied to the mouse cursor
Completed
Last Updated: 16 Jul 2019 08:20 by ADMIN
Release LIB 2019.2722 (7/22/2019)
ADMIN
Created by: Dinko | Tech Support Engineer
Comments: 0
Category: Window
Type: Bug Report
2

			
Completed
Last Updated: 17 Jul 2019 15:00 by ADMIN
Release LIB 2019.2.722 (7/22/2019)

This is reproducible when you disable the automation peers by setting the AutomationManager.AutomationMode static property to Disabled.

It happens when you open a new RadWindow dialog (using the ShowDialog method), and the close it. After this, when you interact with the main window (click a button, hover a GridView, etc.) the exception occurs.

The exception is thrown only in the Output pane of Visual Studio and it doesn't cause any harm to the application. You can safely ignore it.

The exception message is "Invalid window handle".

To work this around you can enable the "Enable Just My Code" option in Visual Studio.

Completed
Last Updated: 07 Nov 2019 11:19 by ADMIN
Release LIB 2019.3.1111
When the RadWindow is initialized on a monitor and then another monitor with higher resolution is added during runtime, moving the RadWindow to the monitor with higher resolution, causes the RadWindows' width and height to be limited to the ones of the initial monitor.
Completed
Last Updated: 25 Apr 2022 08:53 by ADMIN
Release R2 2020 SP1

If the autohiding feature of the taskbar is enabled and RadWindow is maximized, the taskbar is not displayed when the mouse is over the bottom of the screen.

This is observed also in RadTabbedWindow.

Completed
Last Updated: 21 May 2021 06:38 by ADMIN
Release LIB 2021.2.525 (25/05/2021)
Setting the dpiAware attribute to True in the app.manifest file is making the WPF application DPI aware. In this case, the resizing of RadWindow doesn't work properly on two monitors with different DPI scale factors.
1 2 3