Closed GoogleCodeExporter closed 9 years ago
Original comment by dbenamy
on 29 Nov 2007 at 4:32
Goddamnit, now I can't reproduce it.
Original comment by dbenamy
on 11 Dec 2007 at 8:32
I no longer believe you. Closing until somebody can prove it to me; this one
looks
quite fine in careful testing.
Original comment by zac...@gmail.com
on 12 Dec 2007 at 10:09
oh oh! i meant to tell you guys i had a realization about this issue. are we
sure
what appears to be overshooting isn't the effect of a blob force after a
physical
move stopped?? i noticed this the other day.
in other words, you have two blobs that are close together. your turn consists
of
moving one blob a not-too-far distance away and the other blob just activate its
push. the push will (and should) affect the moved blob's final position.
if we still can't reproduce this, i'd bet blob forces are behind it.
Original comment by morales....@gmail.com
on 12 Dec 2007 at 10:30
I can reproduce it now. The effects seem to be larger the fast the blob is
moving (or
maybe the smaller it is). To reproduce:
1. Get a small blob.
2. Have it move across the whole board.
3. It will overshoot. You can use the background as a reference to see it.
Original comment by dbenamy
on 14 Dec 2007 at 2:28
Original comment by dbenamy
on 15 Dec 2007 at 8:50
I think it happens sometime, but it's very minimal. For example, a size 2
small blob
might overshoot by a quarter of its diameter. I would lower the priority on
this.
Original comment by gene...@gmail.com
on 15 Dec 2007 at 4:59
Fixed @ rev 484.
Original comment by zac...@gmail.com
on 16 Dec 2007 at 11:08
Original issue reported on code.google.com by
dbenamy
on 29 Nov 2007 at 4:28