It would help to use RadWindow like System.Window with: - WindowInteropHelper for correct modal behavior - Set window in task bar, also set taskbar icon/title - Use RadWindow as MainWindow in Application (set Application.MainWindow property with RadWindow
When a modal RadWindow is opened clicking out side of the Window (the overlay) should make a the Window blink and a sound should be played.
RadWindow.Confirm default button is OK, in order to change that presently we have to extract and modify styles, set FocusManager.FocusedElement binding to Cancel and set the ContentStyle property in code. It would be much more user friendly if this could be controlled by a simple property.
rendering problem is when minimized only
Available in the 2016 Q1 SP1 Release.
Make it possible to be able to drag the Window not only from its Header. In some cases it is useful to be able to drag the RadWindow from within its content.
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.
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.
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.
Available in the 2015 Q3 Release.
Available with the R3 2016 SP1 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.
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.