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

The RadWindow's size shrinks while dragging it on a monitor with high DPI scale which causes it to shake a bit. In other words, the dragging is not smooth.

This was reproduced on a monitor with DPI scale set to 175%.
This is reproducible if you set the RadWindowInteropHelper.AllowTransparency on the RadWindow control (regardless of the value - True or False).
This is more noticeable in .NetCore projects.

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.

The Window gets clipped on the right side when using a dual monitor setup when the taskbar is on the left/right side of the screen and the app must be running maximized on the secondary screen.

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.

Environment: VS Community 2019 (16.0.3), with .NET Framework 4.8 (release version, run-time and developer pack installed), Windows 10 Pro October 2018

Telerik UI version: latest (2019.1.220.45)

 

When VS2019 opened, Telerik UI for WPF should have been found under the "Extension" menu --> Telerik --> Telerik UI for WPF. However, there is only "Telerik UI for WinForms" under "Telerik" now. There is neither "Telerik scenario" in the "Add New Item" window so no RadForms can be created. Manually replacing <Window> in XAML to <telerik:RadWindow> does change the appearance of the window in the designer, but the properties in the Property window does not change accordingly to RadForms but still WPF standard Form ones. Toolboxes shows current lists of Telerik UI for WPF controls and they can be correctly created (at least RadButton). "Repair" in the Progress Control Panel doesn't fix this problem.

 

Thanks!

When creating themed applications using RadControls, the standard Windows MessageBox control looks out of place.  With that in mind, the predefined RadWindows (Alert and Confirm) seem to be natural replacements for a typical MessageBox.  

However, when these dialogs open, they are silent  That is, they don't play any error, warning, or question sounds like the standard MessageBox - which makes them seem "strange" when used as a replacement.

Adding sounds to (for instance) the Alert window is fairly simple and can be accomplished like this:

RadWindow.Alert(new DialogParameters()
{
    Content = new System.Windows.Controls.TextBlock {
        Text = ex.Message, Width = 250, TextWrapping = TextWrapping.Wrap },
    Header = "Update Error",
    Opened = (alertDialog, eventArgs) => System.Media.SystemSounds.Exclamation.Play()
});

Though, it'd be nice if the ability to play a sound was built-in.  I'd suggest that the DialogParameters class used to customize the predefined dialogs be extended to support a SystemSound member of type System.Media.SystemSounds which, if defined, would play the specified sound when the dialog opens.

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.

If you try to show a window, and right afterwards call RadWindow.Alert() or any other prompt dialog, the main window automatically closes.

To work this around show the prompt in the Loaded event handler of the RadWindow.

 

This behavior is presented with the ShowDialog() method of the WPF native Window control. Basically, the ShowDialog() method could return a value (true, false, null). Currently, the method is "void".

Scheduled for:
The fix for this issue will be available with LIB (version 2018.3.1224) scheduled for publishing on Monday, 24th December 2018.

Provide out of box text wrapping in predefined dialogs.

All Windows messageboxes from Win95 have this possibility. 
Telerik in 2018 does not have this possibility, except through additional templates and additional code. 

Why to buy 

Make it possible to add "No" button to the predefined RadWindow.Confirm dialog without the need of custom Template.

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.