Completed
Last Updated: 06 Apr 2022 10:25 by ADMIN
Release LIB 2022.1.406 (06 Apr 2022)

Different foreground value is applied to elements, which are present inside RadBusyIndicator when using the Office2019 theme.

To work this around, set a new value to the Foreground property of the RadBusyIndicator control.

Completed
Last Updated: 07 Mar 2022 15:50 by ADMIN
Release LIB 2022.1.314 (14 March 2022)
Using the Fluent theme with a higher DPI, e.g. 125%, the spinner ellipses of the BusyIndicator appear cut off on the top and bottom when a higher DPI is used and the control is hosted in the DocumentHost of a RadDocking instance.
Completed
Last Updated: 28 Nov 2018 09:19 by ADMIN
Missing biding to Foreground in the ContentPresenter of the control which prevents not styled controls (i.e. TextBlock) not to receive the proper Foreground for the current theme.

Workaround:

add Foreground = "{TemplateBinding Foreground}" to the ContentControl in the ControlTemplate for RadBusyIndicator.

Scheduled for: 
The fix for this issue will be available with LIB (version 2018.3.1203) published on Monday, 3-rd December, 2018. 
 
Completed
Last Updated: 17 Oct 2016 15:08 by ADMIN
Available in LIB version 2016.3.1017, it will be also available in the 2016 R3 SP1 release. 
Unplanned
Last Updated: 03 Aug 2016 10:20 by Ivan
Created by: Ivan
Comments: 0
Category: BusyIndicator
Type: Feature Request
1
It would be great if the details of the animation weren't tied to the theme. For example, if you want the "parading dots" motif, you have to go with Windows8, Windows8Touch, or one of the "2013" themes. 

The control should have an "AnimationStyle" enumeration property, where you can select which animation you want, independent of the theme. Even better, it would be great if you could specify your own animation.

Thanks!
Completed
Last Updated: 11 Aug 2015 08:26 by ADMIN
Available in LIB version 2015.2.810, it will be also available in the 2015 Q3.
Declined
Last Updated: 26 Nov 2015 14:37 by ADMIN
If the IsEnabled property of a control placed inside the BusyIndicator is bound TwoWay and has NotifyPropertyChanged, in non debugging the property stays to False.
Completed
Last Updated: 07 Sep 2015 13:44 by ADMIN
ADMIN
Created by: Telerik Admin
Comments: 2
Category: BusyIndicator
Type: Bug Report
8
If you change the Culture at run-time and reload the control, the new culture doesn't apply.
Won't Fix
Last Updated: 15 Jan 2016 16:04 by ADMIN
If Hyperlink are placed in the content of the control while the IsBusy is set to true, those links are disabled.
Won't Fix
Last Updated: 16 Jan 2016 18:41 by ADMIN
Setting the Foreground property applies only to the BusyContent rather then the other content inside the control.
Completed
Last Updated: 11 Aug 2016 14:04 by ADMIN
The title is accurate but the description is pretty far off. The problem is that a RadBusyIndicator with a DisplayAfter of 1.5 seconds and IsBusy=true  will initially set its contents to disabled and then enable the contents when IsBusy becomes false.  The
Declined
Last Updated: 05 Jan 2017 15:26 by ADMIN
RadBusyIndicator throw error when theme is Metro and is not set as an Application theme. Message=Cannot access Freezable 'System.Windows.Media.SolidColorBrush' across threads because it cannot be frozen.
Workaround:
Whenever you are running metro styled telerik components you must invoke:
MetroColors.PaletteInstance.Freeze();
So the shared color resources we bind our controls to could be frozen and become thread safe. The above line could be placed in the OnStartup in your example and it would work.
Completed
Last Updated: 11 Aug 2016 14:04 by ADMIN
ADMIN
Created by: Telerik Admin
Comments: 0
Category: BusyIndicator
Type: Bug Report
9
Available in LIB version 2015.3.1207,  it will be also available in the 2016 Q1 release.
Completed
Last Updated: 05 Jan 2017 15:21 by ADMIN
please test again and add steps to reproduce