Won't fix
Last Updated: 23 Nov 2018 15:29 by ADMIN
Multiple operations applied on a big RadBitmap can cause OutOfMemoryException because of used and not disposed unmanaged resources in a WriteableBitmap object.

Steps to reproduce:
- Execute multiple times the Rotate tool
Observe: The memory goes up and retains such.
Expected: The unmanaged memory is cleared.

Findings: the memory leak is related to the WPF class WriteableBitmap which is internally used by the RadBitmap. Attached is a sample project illustrating the problem using only WPF classes.
Note: At this point, we are not aware of a possible fix.
Won't fix
Last Updated: 21 Nov 2018 15:53 by ADMIN
ADMIN
Created by: Stefan
Comments: 0
Category: ContextMenu
Type: Bug Report
0

			
Won't fix
Last Updated: 25 Oct 2018 14:07 by ADMIN
When using an ItemContainerStyle on the second(non-root) BarItems, the Background doesn`t apply
Won't fix
Last Updated: 18 Oct 2018 10:23 by ADMIN
When the properties are bound in code behind, they are not updated as they are supposed to.

Binding them in XAML, by setting the DataContext of the control as StaticResource, works as expected.
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: 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: 02 Oct 2018 11:05 by ADMIN
Won't fix
Last Updated: 21 Jun 2018 14:50 by ADMIN
Won't fix
Last Updated: 23 Feb 2018 08:00 by ADMIN
Won't fix
Last Updated: 05 Feb 2018 11:15 by ADMIN
ADMIN
Created by: Telerik Admin
Comments: 0
Category: Slider
Type: Bug Report
5
When the slider is placed inside a ScrollViewer and the scrollviewer is resized fast a "Layout cycle exception is thrown".

The original scenario where we reproduce the exception is the following:
SelectionStart, SelectionEnd, Minimum and Maximum of the Slider are bound to DateTime.Ticks via converter.
Exception is not reproduced if you move the Mininum declaration in xaml before the Maximum. And same for SelectionStart = before SelectionEnd.

We are closing this item due to the workaround and the fact that it is NOT reproducible in WPF.

If your scenario is different, please open a new support thread with more information regarding this exception.
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.

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

Won't fix
Last Updated: 01 Aug 2017 08:44 by ADMIN
When the Slider ControlTemplate is edited in Blend, the ticks of the control are not displayed.

Workaround:
The ItemsSource and ItemTemplateSelector of the RadTickBar controls "BottomTickBar" and "TopTickBar" is not set in the extraction process. To workaround this, set these two properties of TickBars and the ticks will be displayed ", for instance:
ItemsSource="{TemplateBinding ResultTicks}" and ItemTemplateSelector="{TemplateBinding TickTemplateSelector}".

Reason for closed:
This is an issue, that has been reported to Microsoft on several occasions (for example here: https://connect.microsoft.com/VisualStudio/feedback/details/677461/msdn-forum-the-value-of-itemscontrol-itemssource-is-missing-in-the-extracted-template )  and it is not scheduled to be fixed.
Won't fix
Last Updated: 05 Jun 2017 10:24 by ADMIN
ADMIN
Created by: Konstantina
Comments: 4
Category: DatePicker
Type: Bug Report
1

			
Won't fix
Last Updated: 29 Mar 2017 14:06 by ADMIN
Exceptions are occuring on ALL bindings, not just with RelativeSource

Command="{Binding AddCommand}"

will also raise an exception.
Won't fix
Last Updated: 30 Jan 2017 09:46 by ADMIN
This feedback item is duplicated. Here is the link to the original bug report: https://feedback.telerik.com/Project/143/Feedback/Details/145511-richtextbox-incorrect-layout-and-export-of-bi-directional-mixed-text-containin
Won't fix
Last Updated: 25 Jan 2017 13:11 by ADMIN
Place a RadComboBox in the GridViewColumn header and set SelectedIndex in the xaml. The SelectionChanged event is fired, but the command is not executed.

As a workaround you can set the SelectedIndex in xaml instead of on the Loaded event,
Won't fix
Last Updated: 23 Jan 2017 12:23 by ADMIN
When the SelectedIndex property is read during animation the CLR wrapper will throw InvalidCastException because of invalid cast to int. The object returned from GetValue is DeferredReference object.
Won't fix
Last Updated: 03 Jan 2017 20:51 by ADMIN
ADMIN
Created by: Telerik Admin
Comments: 3
Category: ComboBox
Type: Bug Report
3
See the supported thread.
Won't fix
Last Updated: 29 Dec 2016 14:37 by ADMIN
ADMIN
Created by: Telerik Admin
Comments: 0
Category: TreeView
Type: Bug Report
4
This issue is applicable to Silverlight ONLY!

We have a RadTreeView with following properties IsLoadOnDemandEnabled="True", IsVirtualizing="True" and SelectionMode="Extended" set.
We select an element, collapse his parent and select another item. At this point if we expand the previously parent, both the newly selected item and the the first selected item are selected.
It is not correct the first item to preserve its selection state.

The XAML team has recently reviewed this issue and will not be addressing it as at this time the team is focusing on the bugs impacting the highest number of developers. If you have encountered this issue and it is blocking for your work please contact us through the support ticketing system with details on your setup and a reference to this item.

1 2 3 4 5 6