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: 22 Jan 2016 13:04 by ADMIN
Completed
Last Updated: 25 Oct 2016 14:04 by ADMIN
Completed
Last Updated: 12 Oct 2015 06:13 by Wade
Available in the 2015 Q3 Release.
Completed
Last Updated: 25 May 2015 14:02 by ADMIN
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: 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: 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: 16 Jul 2019 08:20 by ADMIN
Release LIB 2019.2722 (7/22/2019)
ADMIN
Created by: Dinko
Comments: 0
Category: Window
Type: Bug Report
2

			
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: 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: 23 Jun 2014 07:24 by ADMIN
Completed
Last Updated: 12 Oct 2015 06:12 by ADMIN
ADMIN
Created by: George
Comments: 0
Category: Window
Type: Bug Report
1
Place Expander as content in RadWindow. Once expanded, the SizeToContent feature stops working as expected.
Available in the 2015 Q3 Release.
Completed
Last Updated: 12 Oct 2015 06:12 by Licensing
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.
Completed
Last Updated: 08 Aug 2016 14:19 by ADMIN
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.
Completed
Last Updated: 14 Jul 2015 06:14 by ADMIN
It happens when IsRestrictedWhenMaximized set to true.
1 2