by **uckelman** » January 20th, 2008, 8:32 pm

I'm looking at this bug now. I think it's going to be difficult to correct

completely, since there are many places in VASSAL where we do integer

division or downcast doubles to ints. Anyway, it's not clear to me that

rounding to the nearest integer will be sufficient to correct this, as the

once rounding error is accumulated there's no guarantee that it will be

cancelled out after 360 degrees of turns.