Jul 21, 2008 at 5:37 AM
I think you will be better off using the StoryBoard instead of the DispatchTimer.

Microsoft handles the StoryBoard, from a threading context, much better than the DispatchTimer.

The DispatchTimer, is not really threaded, it is queued inside the UI thread.  The Storyboard is also capable of much finer timing control than the DispatchTimer.

There shouldn't really be a difference, but there is due to the design used by MS.
Jul 28, 2008 at 9:11 PM
I changed back to using the Storyboard, but had the same issues as before. The main problem is that the rendering occurs in the timer/storyboard and when it uses more time than the frequency is set to it "misses" the event and the next frame is not rendered. I need to change this architecture, I guess I could introduce a DependencyObject to the Application control that the timer/storyboard would change so an event would be fired in managed code. This is the latest of my ideas, but haven't gotten around to testing it.  Hopefully it works.

Thanks for the input.