Won't Fix
Last Updated: 16 Jun 2021 14:03 by ADMIN
When the RadWindow is declared in XAML and is used as a main window, it won't show in the designer by simply merging the required theme resources and defining an implicit style based on the RadWindowStyle.

Tested with 16.8.4 - works as expected. Updated to 16.9.0 to match the client's setup and managed to reproduce the issue. The issue is reproducible also with the 16.10.0 version of Visual Studio.


Completed
Last Updated: 11 Jun 2021 12:05 by ADMIN
Release R2 2021 SP
When the value of the IsTopMost property of a RadWindow is changed during runtime and then another RadWindow is shown, an ArgumentOutOfRangeException is thrown.
Completed
Last Updated: 21 May 2021 10:19 by ADMIN
Release LIB 2021.2.525 (25/05/2021)

If you open the window on a specific resolution, maximize it and then change the resolution to a bigger one, the window size is not updated. The window stays in the original resolution of the screen.

To work this around subscribe to the SystemEvents.DisplaySettingsChanged event and reset the WindowState of RadWindow.

public MainWindow() // where MainWindow is RadWindow
{
	InitializeComponent();
	SystemEvents.DisplaySettingsChanged += SystemEvents_DisplaySettingsChanged;
}

private void SystemEvents_DisplaySettingsChanged(object sender, EventArgs e)
{
	if (this.WindowState == WindowState.Maximized)
	{
		this.WindowState = WindowState.Normal;
		this.WindowState = WindowState.Maximized;
	}
}

Completed
Last Updated: 21 May 2021 10:19 by ADMIN
Release LIB 2021.2.525 (25/05/2021)
The window is not correctly resized when it is maximized and the taskbar is moved from vertical to horizontal or vice versa 
Completed
Last Updated: 21 May 2021 06:38 by ADMIN
Release LIB 2021.2.525 (25/05/2021)
Setting the dpiAware attribute to True in the app.manifest file is making the WPF application DPI aware. In this case, the resizing of RadWindow doesn't work properly on two monitors with different DPI scale factors.
Declined
Last Updated: 07 Apr 2021 10:38 by ADMIN

Hi,

Please see attached project,

After use animation changed window size and use the mouse to drag to change the size of the window,

When the window size is smaller than the original size, the upper right button will be hide,

Original WPF Window no this problem, And changing size animation very Smooth then RadWIndow.

Completed
Last Updated: 09 Mar 2021 12:29 by ADMIN
Release LIB 2021.1.315
ArgumentOutOfRangeException can be thrown when showing/closing windows in a multi-threaded application. Here's a possible stack trace:

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at System.ThrowHelper.ThrowArgumentOutOfRangeException()
   at System.Collections.Generic.List`1.RemoveAt(Int32 index)
   at System.Collections.Generic.List`1.Remove(T item)
   at Telerik.Windows.Controls.RadWindowManager.RemoveWindow(WindowBase window)
   at Telerik.Windows.Controls.WindowBase.OnClosed()
   at Telerik.Windows.Controls.RadWindow.OnClosed()
   at Telerik.Windows.Controls.WindowBase.CloseHostImidiately()
   at Telerik.Windows.Controls.WindowBase.TryClose(Boolean shouldCloseHost)
   at Telerik.Windows.Controls.WindowBase.Telerik.Windows.Controls.InternalWindow.IWindowDragAware.TryClose(Boolean shouldCloseHost)
   at Telerik.Windows.Controls.InternalWindow.WindowWithNoChromeWindowHost.OnWindowClosing(Object sender, CancelEventArgs e)
   at System.Windows.Window.OnClosing(CancelEventArgs e)
   at System.Windows.Window.WmClose()
   at System.Windows.Window.WindowFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
Declined
Last Updated: 10 Feb 2021 13:39 by ADMIN
Completed
Last Updated: 01 Feb 2021 06:16 by ADMIN
Release LIB 2021.1.201 (2/1/2021)
Completed
Last Updated: 05 Nov 2020 15:12 by ADMIN
Release LIB 2020.3.1109 (11/09/2020)
Changing the ResponseButton through the DefaultFocusedButton property of the DialogParameters does not work in the Office2019 theme.
Completed
Last Updated: 21 Sep 2020 10:56 by ADMIN
Release LIB 2020.3.921 (09/21/2020)
This behavior can be observed when the ResizeMode property of RadWindow is set to CanResizeWithGrip. 
Completed
Last Updated: 17 Aug 2020 12:24 by ADMIN
Release LIB 2020.2.617
This could appear on virtualization systems like Citrix and Systancia. The exception appears in the TaskbarHelper.GetAppBarData() method.
Completed
Last Updated: 10 Jun 2020 13:32 by ADMIN
Release R2 2020 SP1

If the autohiding feature of the taskbar is enabled and RadWindow is maximized, the taskbar is not displayed when the mouse is over the bottom of the screen.

This is observed also in RadTabbedWindow.

Completed
Last Updated: 20 Jan 2020 07:21 by ADMIN
Release LIB 2020.1.120 (1/20/2020)

Hello,

 

I've found a new bug regarding per-monitor DPI awareness in the latest WPF controls build (2020.1.115).

Applications start fine on the modern Windows 10 systems (1607 or later) but crash on previous Windows versions.

The conditions to reproduce:

  • The application is launched on Windows version older than Windows 10 1607/Windows Server 2016. I've reproduced it on Windows 8.1/Windows Server 2012 R2, but I suppose it also affects Windows 10 1507/1511, and probably Windows 8/Windows Server 2012.
  • Application manifest contains:
<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true/PM</dpiAware>

Here is the stack trace:

System.EntryPointNotFoundException: Unable to find an entry point named 'GetDpiForSystem' in DLL 'User32.dll'.

   at Telerik.Windows.Controls.InternalWindow.Standard.NativeMethods.GetDpiForSystem()

   at Telerik.Windows.Controls.InternalWindow.Standard.DpiHelper.GetSystemScaleFactor()

   at Telerik.Windows.Controls.InternalWindow.Standard.DpiHelper.CalculateScaleFactor(IntPtr hwnd)

   at Telerik.Windows.Controls.InternalWindow.Standard.DpiHelper.GetPerMonitorDPIAwareScaleFactor(IntPtr hwnd)

   at Telerik.Windows.Controls.InternalWindow.ChromelessWindowHelper.<Initialize>b__81_0(Object sender, EventArgs args)

   at System.Windows.Window.OnSourceInitialized(EventArgs e)

   at System.Windows.Window.CreateSourceWindow(Boolean duringShow)

   at System.Windows.Window.CreateSourceWindowDuringShow()

   at System.Windows.Window.SafeCreateWindowDuringShow()

   at System.Windows.Window.ShowHelper(Object booleanBox)

   at System.Windows.Window.Show()

   at Telerik.Windows.Controls.InternalWindow.WindowWithNoChromeWindowHost.Open(Boolean isModal)

   at Telerik.Windows.Controls.WindowBase.ShowWindow(Boolean isModal)

   at Telerik.Windows.Controls.RadWindow.Show()

   at TelerikWpfCrash.App.OnStartup(StartupEventArgs e) in C:\Users\fedarovich\source\repos\Test\TelerikWpfCrash\TelerikWpfCrash\App.xaml.cs:line 20


The issue happens because the code calls the WinAPI functions not available on these OS versions (for example, GetDpiForSystem, but maybe there are more). 

I've attached a small example to reproduce this issue. It is for .Net Core 3.1, but the same issue exists in .Net Framework too.

Declined
Last Updated: 17 Jan 2020 15:26 by ADMIN

Hi,

   There is a bug in version 2019.3.1023.45 RadWindow when I minimum and restore window from task bar

Completed
Last Updated: 25 Nov 2019 10:00 by ADMIN
Release LIB 2019.3.1125 (11/25/2019)
This exception is thrown when the CanExecute method of the Command bound to a response button returns false when the response button key is pressed. 
Completed
Last Updated: 13 Nov 2019 15:50 by ADMIN
Release LIB 2019.3.1118
The Window doesn't resize correctly when dragged from the primary monitor (with taskbar) and docked to the top of the screen of a secondary monitor (no taskbar) in order to maximize it and "Show window contents while dragging" Windows system setting is disabled.
Completed
Last Updated: 07 Nov 2019 11:19 by ADMIN
Release LIB 2019.3.1111
When the RadWindow is initialized on a monitor and then another monitor with higher resolution is added during runtime, moving the RadWindow to the monitor with higher resolution, causes the RadWindows' width and height to be limited to the ones of the initial monitor.
Completed
Last Updated: 05 Nov 2019 08:10 by Andrew
Created by: Andrew
Comments: 4
Category: Window
Type: Bug Report
1

After fixing this BUG (Release LIB 2019.3.930), an additional issue is found.

A window is in Maximized or Normal state, click on the application icon in the taskbar to minimize it and click again to restore the window. It gets clipped to ~160*26 pixels. After clicking on this header, it gets restored to Maximized or Normal state depending on the initial state.

I have a two-monitor setup with identical resolutions (FullHD on both monitors) and Scale is 100% on both monitors.

Completed
Last Updated: 27 Sep 2019 12:36 by ADMIN
Release LIB 2019.3.930

Initial BUG was fixed in recent update.

One issue still exists:

When minimizing a window that is maximized in the way the intial issue described the problem, and you reactivate it by clicking on its "TaskBarIcon", the window gets clipped incorrectly again.

1 2 3 4