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.

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.

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: 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.
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.


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.
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. 
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.
1 2