When the UI culture changes, the DataMemberBinding is updated for all columns (I'm wondering why?). See \Controls\GridView\GridView\GridView\GridViewDataControl.cs:

private void UpdateCultureInfoIfNeeded()
{
	if (this.cultureInfo != null && (this.cultureInfo.Name.ToUpper(this.cultureInfo) != this.Language.IetfLanguageTag.ToUpper(this.cultureInfo)))
	{
		this.InitializeCultureInfo();
		foreach (var column in this.Columns.OfType<GridViewBoundColumnBase>())
		{
			Binding oldBinding = column.DataMemberBinding.CloneBinding(column.ValidatesOnDataErrors);
			column.DataMemberBinding = oldBinding;
		}
	}
}

However, if the DataMemberBinding was null, the CloneBinding creates a new binding with empty path instead of returning null again - but this never makes sense for the DataMemberBinding on a column (crashes the application as soon as the Binding is applied to the cells).

Background: I have created a column where the cell value is not bound but dynamically calculated - so the DataMemberBinding is null.

The fix will be included in our LIB v. 2015.02.0810.

Coming from RadControls for WinForms I did miss this control.
It didn't take me long to create my own alert controls, but it would be nicer to have them styled and behave like all other telerik controls.

Hello,
I am launching standalone Telerik Report Designer from our application to edit custom reports stored in a database.
I was able to inject the application custom functions assembly reference into designer`s config before launching it and it works fine.
But I was not able to inject the application connection string into designer`s config before launching it because the designer does not use global ConnectionStrings section, but custom ConnectionStrings section in userSettings which makes it problematic to update.
Can You change the designer to allow usage of ConnectionStrings from the designer`s global config section or provide another means?
That is essential to render reports successfully with correct data, because the reports use named connection strings.
I preffer this instead of changing all connection strings in report`s data sources.

Thank You

Marek Istvanek
HaSaM
Czech Republic

Add new control to the suite: Wizard control.

I am currently working with MaskedInput control, and I have an issue on your documentation.  Why is there no explanation on all the properties, even in your demo there are a lack of explanation.  For instance, SpinMode, what is this, what does it do?
IsManinulationEnabled, what does this do, under which control, the Numeric,, Decimal, DateTime or Text???  Why Text and Value.   What is OriginalValue means? The control have an AcceptsReturn properties, why not an AcceptsTab properties?

When you place items in the gallery there are scenarios where the tooltip of the scroll up/down buttons is not correct.

Available in LIB version: 2014.3.1402

Available in Q3 2014.

Similar to the Windows8 RadRadialMenu

RadRadialMenu is available in Q3 2014.

ContentStringFormat is not respected for ToolTip in VisualStudio2013 theme

Resolved with lib version 2014.2.908.

PasswordBox: Content cannot be selected and cursor is missing-Windows8 theme

This problem is resolved with lib version 2014.2.721.

Telerik separator style overrides default appearance of separators that are not children of StatusBar 

New TimeLine control featuring ZoomBar.

Sometimes when Tab is pressed I get this exception:
An unhandled exception occured in the application
Message: Object reference not set to an instance of an object.
Exception type: System.NullReferenceException
Details:
   at Telerik.Windows.Controls.Input.FocusScope.FocusInternal() in c:\TB\117\WPF_Scrum\Release_WPF\Sources\Development\Core\Controls\Input\FocusScope.cs:line 146
   at Telerik.Windows.Controls.Input.FocusScope.FocusNextElement() in c:\TB\117\WPF_Scrum\Release_WPF\Sources\Development\Core\Controls\Input\FocusScope.cs:line 54
   at Telerik.Windows.Controls.Input.FocusScope.RemoveFocusableElement(Control element) in c:\TB\117\WPF_Scrum\Release_WPF\Sources\Development\Core\Controls\Input\FocusScope.cs:line 105
   at Telerik.Windows.Controls.Input.FocusScope.FocusableElement_Unloaded(Object sender, RoutedEventArgs e) in c:\TB\117\WPF_Scrum\Release_WPF\Sources\Development\Core\Controls\Input\FocusScope.cs:line 314
   at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   at MS.Internal.FrameworkObject.OnUnloaded(RoutedEventArgs args)
   at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
   at System.Windows.BroadcastEventHelper.BroadcastUnloadedEvent(Object root)
   at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
   at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

I found a memory leak when using RadComboBox inside TabItems that are dynamically added or removed from a TabControl: even if the tab is removed, the TabItem instance stays in memory due to an instance of RadComboBox that is not collected.

If the tab has a DataContext, that may be huge memory parts that cannot be collected!...

Please find enclosed an example of WPF application that helps to reproduce the problem.

When the custom map tiles provider returns the tiles up to the certain zoom level and the user zooms the map to the level above the supported level then the map should use available tiles from previous zoom level, but it show gray patches instead. It occurs when the custom map tiles provider returns null for unavailable tiles.

When user opens the mini map and changes the zoom level of the map then the MapShapeData objects in VisualizationLayer jump and aren't positioned to correct location. This effect is kept even when the user closes mini map.