Big day yesterday. First we had a training session in the morning, and talked about animations. I could see how I got a few things wrong. Animations in XAML are very straightforward to create and start, and it gets a bit more complex when you want to control them and especially stop them. In my ColorClock , I've been confronted to a few of these problems: How to release the animation's "grasp" on the dependency property it just animated? How to "chain" animations, making sure that they are correctly released so that they can eventually be garbage collected? How to synchronize animations? That's where Josh' practical experience really helps! Here are a few tips: To synchronize animations can be important to enhance the application's visual appearance. Simple example: If you have a list of buttons, with one of them flashing (for example with an opacity animation, or a color animation). If you start flashing another of these buttons, it's going to look ugly if they don't flash together. However,
Read More...