The default dialogs for the WPF RadWindow (Prompt, Alert, Confirm) do not seem to allow sizing of the content of the message. I have tried imbedding controls to set width and maxwidth, but I need to use a MaxWidth to prevent horizontal scrollbars. Ideally a Maxwidth parameter would be available allowing longer text message to spread out.

The code below works, but I'm restricted to a narrow dialog.

            Dim Scroller As New ScrollViewer
            Dim TextBlk As New Controls.TextBlock()
            With Scroller
                .HorizontalScrollBarVisibility = ScrollBarVisibility.Disabled
                .VerticalScrollBarVisibility = ScrollBarVisibility.Auto
                If Owner IsNot Nothing Then
                    .MaxHeight = (WPFScreen.GetScreenFromElement(Owner).WorkingArea.Height - 100) 'Do not use entire height
                Else
                    .MaxHeight = (WPFScreen.Primary.WorkingArea.Height - 300) 'Do not use entire height
                End If

                With TextBlk
                    .Margin = New Thickness(10)
                    .TextWrapping = TextWrapping.Wrap
                    .Text = Message
                    'We seem to be stuck with a fixed width available for our text.
                    'If this is increased a horizontal scrollbar appears.
                    .MaxWidth = 230
                End With
                .Content = TextBlk                  'Put textblock in scroller                 
            End With

            Dim RadDialog As New DialogParameters
            With RadDialog
                .Content = Scroller
                .DefaultPromptResultValue = DefaultValue        'Default prompt result
                .DialogStartupLocation = DialogStartupLocation
                .Header = Header
                .IconContent = IconContent
                If ThemeName.ToLower <> "expression_dark" Then ' *NoLoc*
                    .ModalBackground = m_SPIBackgroundBrush
                End If
                .Owner = Owner
                .Closed = New EventHandler(Of WindowClosedEventArgs)(AddressOf OnPromptClosed)  'Reference handler for response
                '.ContentStyle
                '.WindowStyle            
            End With

            RadWindow.Prompt(RadDialog)

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.

Available in LIB version 2015.3.1130, it will be also available in the 2016 Q1 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. 

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.

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

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!

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.

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.

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.