The way to do this is quite straightforward. Rather than wrapping the content within the ScrollViewer with the BusyIndicator, wrap the ScrollViewer itself in the BusyIndicator. This way, the BusyIndicator’s layout will not be affected by the scroll within the ScrollViewer.

-David

Kindly guide me how i can position it with respect to my screen so that whenever iis enabled it appears on the screen to see?

One thing that I noticed that the control supports IDisposable to get rid of the timers. I use this control on several of my grids contained in forms that open and close multiple times. If I do not call Dispose, my forms (and grids) all stay on the garbage collector.

A big improvement would be to come up with a way to use something other than the Timer or have it self clean up.

It is so darn close to being clean where I just paste it into the XAML and I get a nice loading indicator. But if I forget to call Dispose(), I get memory leaks.

by Aquilax

Personally, I get anxious using the “attributing” method, since for something like this it can actually force you to inject things into the visual tree, which could break bindings or otherwise change the logical structure of your application unexpectedly (potentially breaking bindings, etc.).

Anyway, I think it’s more a matter of preference than anything else. I like the composability of the wrapping method. I often have multiple activity controls wrapping my UI — one with “Loading…”, one with “Submitting…”, one with “Working…”, etc., all bound to different properties.