On Thu, 2005-03-31 at 11:22 +0800, Simon Wittber wrote: > > I do not agree with the hiding the step() interface for Physics. You > > *need* to be able to provide the step duration there. Why? It is simple > > - your app has rarely constant framerate. If you couple the framerate to > > the physics sim in a fixed manner (e.g. one frame = one step), you are > > going to get problems with the physics, as each frame takes a slightly > > different amount of time. > > This is true, however I have achieved a solution to both the above > problems using the below class. Using the default arguments, it will > count from 0 to 360 at a rate of 1 unit per second. Try it and see :-) > You could use this class to transparently supply the correct duration > value to the ste() function.
This is similar to what I plan to eventually do in the advance_time method of the simulation class, with interpolation being handled by the bodies themselves.
signature.asc
Description: This is a digitally signed message part
