Comments by snowdogs2 (Top 1 by date)

Yes I was running in debugger, but I've also built a realease version and run that on it's own as well as run without debug and the performance was equally poor. I did however find out that getting rid of the drop shadow effect drastically improves the performance, to acceptable levels. However, Once I start putting things in my pods to make it a practical dashboard I'm concerned that it will start chugging again, because if a drop shadow effect works fine in silverlight and causes WPF to come to a crashing halt, there's no telling what will break WPF.

I've also noticed that most WPF applications have some kind of Framerate issue. When you drag to resize there is a visible black edge along the right and bottom that appears while you resize. It's not just my application, I downloaded a demo on basic animation timing and it has the same effect. However, if I create a default WPF application, with nothing in it resizes without the black shadow. It's seems certain graphic events require more of the system and cause it to slow down. However, I have no idea what causes what to crash and burn. I did a test with the original Silverlight and it has a similar issue with the edge as you resize, but again no issue with the DropShadow. There seems to be some very odd discrepincies in performance, that don't make a lot of sense. One effect works fine in Silverlight, and causes the animation to grind to a halt in WPF. How are to know what effects, settings, overwhelm the animation, in which system. I looked in MSDN on wpf animation tips and tricks, and I didn't see anything the about DropShadow effects, or any settings/effects causing problems.

Finally, as for the Convert.ToDouble, yeah, that was an original draft, I've since changed to "0.0". the TopPropert was being set to null by default in WPF, and had to be set back to 0. There are a number of little quirk differences that I've been noticing that don't quite translate to WPF.

Finally as for the Conver.ToDouble(0), yeah, it was from a first draft. I've since replaced it with 0.0. The Canvas.Top and LeftProperties were being set to Null when moved over to WPF. Took a little while to figure that out, as the exception wasn't pointing right there. I've found a number of little quirky differences when moving from Silverlight to WPF.