Declined
Last Updated: 13 Aug 2019 13:18 by ADMIN
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.
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
Declined
Last Updated: 10 Jul 2019 07:16 by ADMIN

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.

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: 03 Jul 2019 14:27 by ADMIN
Release LIB 2019.2.708 (7/8/2019)
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.
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.
Declined
Last Updated: 21 May 2019 12:43 by ADMIN

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!

Completed
Last Updated: 18 Dec 2018 14:16 by ADMIN
Scheduled for:
The fix for this issue will be available with LIB (version 2018.3.1224) scheduled for publishing on Monday, 24th December 2018.


Approved
Last Updated: 01 Aug 2018 15:54 by ADMIN
Completed
Last Updated: 07 Jun 2018 06:49 by ADMIN
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.
Approved
Last Updated: 21 Dec 2017 16:46 by ADMIN
To resolve this remove the MinWidth setting. You can set it back when the window is restored.

private double myMinWidth;
private void Window_WindowStateChanged(object sender, System.EventArgs e)
{
            var window = (RadWindow)sender;
            if (window.WindowState == WindowState.Minimized)
            {
                this.myMinWidth = window.MinWidth;
                window.MinWidth = 0;
            }
            else
            {
                window.MinWidth = this.myMinWidth;
            }
}
Approved
Last Updated: 16 Nov 2016 11:44 by ADMIN
Completed
Last Updated: 25 Oct 2016 14:04 by ADMIN
Completed
Last Updated: 25 Oct 2016 13:57 by ADMIN
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. 
Declined
Last Updated: 06 Oct 2016 12:44 by ADMIN
The issue is reproducible when the DPI is changed at runtime(new feature introduced with Windows 10) and therefore the application is not notified for the change. In order the application to be aware of the change the user have to logout and sign in (or the application should be DPI aware).
Approved
Last Updated: 19 Sep 2016 14:11 by ADMIN
1 2 3