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.

Let me first second what everyone is saying… great control, great idea! However, I’m having an issue in some cases getting the content to display right. I’m trying to wrap the content of my page within an activity control but the content is no longer stretching horizontally and veritically.

I have a hunch it has less to do with your control and more to do with the other elements on the page, and maybe style conflicts, but I’m not sure where to start. Any attempts I’ve made to set the size of the activity control and the size of child elements has failed. Any suggestions would be appreciated.

Great control, not sure I prefer “wrapping” as opposed to “attributing” though (attached prop).

Thanks,
Mark