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.
Moving a window fast on low performance machine or between two monitors causes incorrect offset to be applied to the mouse cursor
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.
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.
When EventBinding is used in XAML to bind commands to events of Window or RadRibbonWindow (as it inherits Window), InvalidOperationException is thrown in design-time. Workarounds: 1. Attach an event handler directly to the events of the Window (RadRibbonWindow) 2. (more MVVM-friendly) use Behavior to attach the appropriate event handler.
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.
Available with the R3 2016 SP1 release.
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.
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.
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.
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.
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.
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.