Won't Fix
Last Updated: 26 May 2020 15:27 by Petar

" Collection was modified; enumeration operation may not execute.'" - The exception is observed when the CLR exceptions are enabled from Visual Studio. 


The Ellapsed event handler of the Timer is executed in background thread but modifying chart data in a background thread is considered bad practice which is not supported by our component. This is the reason we are declining this bug report.

General solution is to schedule the data update to happen on the UI thread with Dispatcher. When in ViewModel, the following code can be used:

        private void OnTimerElapsed(object sender, ElapsedEventArgs e)
            ViewModelBase.InvokeOnUIThread(() =>
                for (int i = 0; i < Items.Count; i++)
                    Items[i].X += (_random.NextDouble() - 0.5) * 0.1;
                    Items[i].Y += (_random.NextDouble() - 0.5) * 0.1;
Won't Fix
Last Updated: 30 Mar 2020 10:10 by ADMIN
The panel allocates empty space for items that are hidden by setting their Visibility to Collapsed. Such items should be ignored when the panel arranges its items.

To work this around, instead of the Visibility property, you can remove and add the items in the ItemSource collection whenever you need to toggle their visibility.
Won't Fix
Last Updated: 29 May 2020 08:46 by Petar
Cannot parse values when DisplayFormat is set to Long and AllowParsingWithoutSeparator is True.
Won't Fix
Last Updated: 12 May 2020 08:22 by Hans
Tab selection does not work in the VS designer when switching between different views.
Won't Fix
Last Updated: 01 Oct 2019 10:47 by ADMIN
Created by: Viktoria
Comments: 1
Category: GridView
Type: Bug Report
When there are items with longer text than the FilteringControl's default width, the FilteringControl resizes when scrolling to these items. This behavior is observed with all themes, different from Windows 8 and Windows 8 Touch.
Won't Fix
Last Updated: 10 Jul 2019 15:52 by ADMIN
Exporting documents that contain PNG images SMask and ImagesDeflaterCompressionLevel is set to a non-default value may produce a document in which those images are not processed correctly by Adobe reader.
Won't Fix
Last Updated: 04 Apr 2019 13:57 by ADMIN

The content of the cell is set from .LoadContent() method and is returned from the CreateCellElement method of the column. 

One possible scenario for a fix is to change that behavior and apply directly the template as WPF DataGrid does. However, this is a huge breaking change with CreateCellElement method is widely used. The second approach is to leave the code as it is right now, return the element from method of DataTemplate and set the ContentTemplate property of the cell to that DataTemplate. This will cause the content to be loaded twice. Which will degrade the  

So, as it turns out the solution is either to introduce breaking change or degrade the performance. Both of them are against our believes and efforts to improve the controls. 

Our suggestion is to use a workaround -  setting triggers directly to the style. We do hope you understand our concerns. 
Won't Fix
Last Updated: 11 Oct 2019 14:20 by ADMIN

 Group rows which are not present in the view are not visualized when the window is maximized.

A possible solution here is to set the GroupRenderMode property to Flat.

Won't Fix
Last Updated: 22 Feb 2019 15:56 by ADMIN

The fix for this issue will be available with the next LIB (version 2018.3.1224) expected on Monday, December 24.
Won't Fix
Last Updated: 21 Nov 2018 15:53 by ADMIN
Created by: Stefan
Comments: 0
Category: ContextMenu
Type: Bug Report

Won't Fix
Last Updated: 11 Oct 2018 08:28 by ADMIN
The vertical scrollbar measure incorrectly when the control's ItemsSource is populated in its Loaded event. To reproduce this, set the ItemsSource when the control is initialized. And then populate it on Loaded. Also, to reproduce this you will need to define the columns manually.

To resolve this, populate the data on initialization of the gridview. Or delay the population to happen after the Loaded event. You can use a dispatcher for this.
Won't Fix
Last Updated: 23 Aug 2019 16:18 by ADMIN
"Win32Exception (0x80004005): Not enough storage is available to process this command" is thrown when multiple RadDocument instances are created in background threads. 

This is due to the fact that RadDocument contains MailMergeDataSource object, which is DependencyObject. When multiple dependency objects are created in different threads, they are not property freed by thread's Dispatcher.

Workaround 1: Microsoft provided workaround in a bug report here:
https://connect.microsoft.com/VisualStudio/feedback/details/620588/system-componentmodel-win32exception-0x80004005-not-enough-storage-is-available-to-process-this-command , namely:
Put the following code:

Dispatcher dispatcher = Dispatcher.CurrentDispatcher;

anywhere in the background thread processing the RadDocument.

Workaround 2: Use pooling of the used threads. The problem is that Task Parallel Library (which has built-in pooling) does not use STA threads by default, but this can be achieved by using custom TaskScheduler (attached, the code is get from here: https://code.msdn.microsoft.com/ParExtSamples ):

            var parallelOptions = new ParallelOptions()
                TaskScheduler = new StaTaskScheduler(Environment.ProcessorCount)

            Parallel.For(0, 10000, parallelOptions, cc =>
                    var document = new DocxFormatProvider().Import(data);
                    byte[] pdfBytes = new PdfFormatProvider().Export(document);

Won't Fix
Last Updated: 02 Oct 2018 11:05 by ADMIN
Won't Fix
Last Updated: 08 Feb 2019 15:23 by ADMIN
This behavior is reproducible when we have applied Material theme and we have disabled the selection and drag of a RadTreeViewItem. 
A possible workaround is to set the MaterialAssist.CheckedBrush attached property to Null of the RadTreeViewItem which you don't want to select and drag.


 <telerik:RadTreeViewItem Header="RootItem" material:MaterialAssist.CheckedBrush="{x:Null}" />
Won't Fix
Last Updated: 08 Oct 2018 14:54 by ADMIN
For the time being, an appropriate converter should be used for the bindings.
Won't Fix
Last Updated: 15 Oct 2019 11:36 by ADMIN
When an application is built with .net version 4.7, the paragraph dialog is clipped in the bottom.
Won't Fix
Last Updated: 21 Jun 2018 14:50 by ADMIN
Won't Fix
Last Updated: 25 Oct 2017 16:16 by ADMIN
In a two monitors scenario the ApplicationMenu appears on the left monitor when the RibbonView with negative left margin is hosted in a RibbonWindow which is maximized on the right monitor.

We are closing this issue as the described behavior as expected. When logged first, the negative left margin of RibbonView was not taken into account.
When popup opens and its parent starts on the left monitor, popup calculates that it cannot fit entirely and changes its direction of opening. This expected by the WPF Framework.
When you give negative left margin of the RibbonView, its application button might also goes with 1-2 (or more) pixels on the left monitor. Then popup (the application menu opens in a popup) has no space and changes its opening direction to left.
This is expected and the only reasonable solution would be changing the negative left margin to positive or 0.

1 2 3 4 5 6