Comments on: A Simple WPF Loading Animation http://www.brianlagunas.com/index.php/2009/08/21/a-simple-wpf-loading-animation/ Fri, 16 Jul 2010 17:01:48 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Brian Lagunas http://www.brianlagunas.com/index.php/2009/08/21/a-simple-wpf-loading-animation/comment-page-1/#comment-56 Brian Lagunas Wed, 05 May 2010 01:42:04 +0000 http://brianlagunas.com/2009/08/21/a-simple-wpf-loading-animation/#comment-56 I would be interested in seeing your test specifications and result documentation. I personally have not experienced this type of behavior on either hardware tier. Could you share your test specs, results, hardware configuration, and you application implementation? I am very intrigued by this performance problem. I would be interested in seeing your test specifications and result documentation. I personally have not experienced this type of behavior on either hardware tier. Could you share your test specs, results, hardware configuration, and you application implementation? I am very intrigued by this performance problem.

]]> By: Troy http://www.brianlagunas.com/index.php/2009/08/21/a-simple-wpf-loading-animation/comment-page-1/#comment-55 Troy Tue, 04 May 2010 17:41:48 +0000 http://brianlagunas.com/2009/08/21/a-simple-wpf-loading-animation/#comment-55 Actually, the animation is a culprit for CPU usage. There is a 3 tier graphics rendering level, http://msdn.microsoft.com/en-us/library/ms742196.aspx. I've been looking into this recently as a project I work on uncovered this as the problem to our terrible performance on some test systems. I ran this animation on a test system that is in the tier 0 category and the CPU usage stayed between 25-30%. I've been trying to find a replacement "waiting" indicator so our performance doesn't suffer. With newer systems in tier 2 you shouldn't see a performance hit. Actually, the animation is a culprit for CPU usage. There is a 3 tier graphics rendering level, http://msdn.microsoft.com/en-us/library/ms742196.aspx. I’ve been looking into this recently as a project I work on uncovered this as the problem to our terrible performance on some test systems. I ran this animation on a test system that is in the tier 0 category and the CPU usage stayed between 25-30%. I’ve been trying to find a replacement “waiting” indicator so our performance doesn’t suffer. With newer systems in tier 2 you shouldn’t see a performance hit.

]]> By: Brian Lagunas http://www.brianlagunas.com/index.php/2009/08/21/a-simple-wpf-loading-animation/comment-page-1/#comment-37 Brian Lagunas Tue, 30 Mar 2010 14:09:04 +0000 http://brianlagunas.com/2009/08/21/a-simple-wpf-loading-animation/#comment-37 I am confident that the animation is not the culprit in your CPU usage problem, and you may have an underlying problem. The way I normally use a loading animation in WPF is in combination with a background worker thread. This allows my long running process to occur on the background thread, while my animation shows the user that something is happening. So, lets say my animation's visibility property is data bound to an IsBusy property in my ViewModel. IsBusy = true; //starts the animation BackgroundWorker worker = new BackgroundWorker(); worker.DoWork += delegate { //Long running process }; worker.RunWorkerCompleted += delegate(object sender, RunWorkerCompletedEventArgs e) { IsBusy = false; //stops the animation }; worker.RunWorkerAsync(); Hope this helps. I am confident that the animation is not the culprit in your CPU usage problem, and you may have an underlying problem. The way I normally use a loading animation in WPF is in combination with a background worker thread. This allows my long running process to occur on the background thread, while my animation shows the user that something is happening. So, lets say my animation’s visibility property is data bound to an IsBusy property in my ViewModel.

IsBusy = true; //starts the animation
BackgroundWorker worker = new BackgroundWorker();
worker.DoWork += delegate
{
//Long running process
};
worker.RunWorkerCompleted += delegate(object sender, RunWorkerCompletedEventArgs e)
{
IsBusy = false; //stops the animation
};
worker.RunWorkerAsync();

Hope this helps.

]]> By: Peter http://www.brianlagunas.com/index.php/2009/08/21/a-simple-wpf-loading-animation/comment-page-1/#comment-36 Peter Tue, 30 Mar 2010 13:43:36 +0000 http://brianlagunas.com/2009/08/21/a-simple-wpf-loading-animation/#comment-36 This animation is really nice, but it takes like 25% of CPU and when i'm trying to put in my app i've got some troubles with the starting animation and can't resolve it. This animation is really nice, but it takes like 25% of CPU and when i’m trying to put in my app i’ve got some troubles with the starting animation and can’t resolve it.

]]>