actually thinking about it.. detect a collision then go back and step through is probably not a good idea as it could actually miss a glancing blow.
if the ball is moving faster than 1pixel per update and it passes close to the corner it may end up not detecting that it had actually collided with the corner halfway through the move.
You'd be better off on every update to find the fastest moving object and then use that to determine how timeslices are required to ensure nothing moves more than 1 pixel per slice.
if the ball is moving faster than 1pixel per update and it passes close to the corner it may end up not detecting that it had actually collided with the corner halfway through the move.
You'd be better off on every update to find the fastest moving object and then use that to determine how timeslices are required to ensure nothing moves more than 1 pixel per slice.