You can still use a timer if you want.
If you want to render per frame, like in DX, you use the
CompositionTargert.Render event to get called per frame. This feature should
be used when you need to apply physics or collision detection on objects, and
your animations are very quick.
You could use the animation engine to move your object around, but doing
during a mouse move seems to quick for me...and I would use frame based
If you are new to WPF, I would recommend getting a book on it. Trying to
learn via blogs may not be helpful because a lot of the community is past the
learning phase, and you will get much more complicated samples which won't
make any sense without learning the basics first.
Petzold book can be bought, and Adam Nathan and Chris Anderson's book will
be released shortly. I think all 3 of these book take a different approach to
teaching the material. It's all good stuff..including the SDK which has a lot
of nice samples and Overview reading - including a nice sample on frame based
> I'm working on a simple bouncy ball app... all I want is a little
> Ellipse to bounce around the window hitting each edge and bouncing the
> other way. In Windows Forms I would have used a timer, set to 50ms and
> on each frame i'd set the location of the Ellipse to a new spot. I
> understand now that there's timelines for this sort of thing, but this
> just seems to be for a animation with no logic. All I want to do is set
> the ball to a new location and animate it bouncing around. Any
> recommendations on how to do this?
> - Ben Friedland