[Solved] Busy Indicator stop to work

[Jose Jones]

Hi...

We are building an application using RadTabManager.  On one specific view, the RadBusyIndicator runs well up until a certain time. 



Here's the code for the view : no rocket science here...  The BusyIndicator IsBusy property is binded to IsLoading property of my view model.  I added a small label (textblock) where the visibility is binded to the same attribute and it works just fine at any time. 



I try to understand the issue.  I guess that it's not related to the IsLoading property of my view model, as I would face the same issue with my textblock. 



Maybe someone could give me an advise on how to debug that situation?



Thanks for your help

<Grid>
      <Grid.ColumnDefinitions>
          <ColumnDefinition  />
      </Grid.ColumnDefinitions>
      <Grid.RowDefinitions>
          <RowDefinition Height="Auto" />
          <RowDefinition Height="*" />
          <RowDefinition Height="Auto" />
      </Grid.RowDefinitions>

      <!-- Header with hyperlink -->
      <frameworkControls:HeaderControl Grid.Row="0"
                                       HeaderImageSource="{Binding Path=HeaderImage}"
                                       TopLeftAlignText="{Binding Path=RessourceInfo.Description}"
                                       BottomLeftAlignText="{Binding Path=SelectedTimesheetType, Converter={StaticResource EnumDescriptionConverter}}"
                                       TopRightAlignText="{Binding Path=PeriodDescription}" />

      <!--Timesheet header-->
      <userControls:TimesheetHeader Grid.Row="1" Margin="5,0,5,0" />

      <!--Timesheet detail-->
      <ContentControl Grid.Row="1" Margin="5,0,5,0"
                      regions:RegionManager.RegionName="{Binding Path=ViewId, Converter={StaticResource ChildRegionNameConverter}, ConverterParameter=TimesheetEntryListRegion}"
                      Style="{StaticResource ContentControlStyle}" />

      <!--BrokenRules-->
      <frameworkControls:FlattenedBrokenRulesControl Grid.Row="2" MaxHeight="150" />

      <!--Wait control-->
      <telerik:RadBusyIndicator Grid.Row="0" Grid.RowSpan="3"
                                IsBusy="{Binding Path=IsLoading, Mode=OneWay}"
                                BusyContent="{Binding LoadingText}" />


      <TextBlock Grid.Row="0" Text="{Binding LoadingText}" FontSize="18"  Visibility="{Binding Path=IsLoading, Converter={StaticResource visibilityConverter}}" />


  </Grid>

[Vladi]

Hello,

We are not sure what the issue exactly is. As the provided code snippets don't show how exactly the RadBusyIdicator is enabled and disabled it is possible that that implementation is the source of the issue.

I created a sample project that shows how to enable and disable the control with the use of a BackgroundWorker, hope this is helpful. If you continue to experience issues could you try to reproduce them i that sample project and send it back to us in a new support thread.

Regards,
Vladi
Telerik

[Jose Jones]

Hello Vladi...

Thank you very much for your example.  Even though we don't explicitly use a Background Thread, we use some async algorithm to execute a bunch of process. 



The different views exposed in our TabManager are injected with PRISM and vuiew



As it works fine for the first couple of executions, it's quite difficult to identify the issue.  I'm unfortunately not able to send you the complete code, as it come with our own Frameworkm and I'm not able to reproduce the issue with simple example.



The only thing I can tell is that the IsLoading property works well, as the textblock, which visibility property is binded to the same IsLoading property of my viewModel, shows and hides itself correctly, even after the RadBusyIndicator stopped working.



Thank you very much for your support!

[Vladi]

Hello,

As the control works as expected initially it looks like some other operation is freezing the thread which is leading to the unexpected behavior.

Unfortunately without being able to observe the issue on our side we cannot provide you with appropriate assistance. If you are able to reproduce the issue in a sample project you can send it to us in a support thread and we will do our best to find the source of it.

Regards,
Vladi
Telerik

[Jose Jones]

I am unfortunately not able to reproduce this issue in a small project....

I have been able to fix though by forcing the DisplayAfter attribute to 0.



Maybe it can help you to resolve the problem...



Thanks for your support

[Vladi]

Hello,

Thank you for providing us with the additional information.

We are glad you found a solution for this issue in your project.

Regards,
Vladi
Telerik