Double move confirmation

[Happy0]

bebot managed to move twice, somehow...

sbot links --dest "%rRPFDrNIGcg6BOgvza4S3pzdYqHUg0kxVorvdD15F10=.sha256" --values

I suspect because the m.redraw (on hiding confirmation) is in a setTimeout, the 'on confirm' click can rarely fire twice, or something... Tricky times.

Need to:

• Disable the 'confirm move' button after the first click. Make sure it's re-enabled on the next move, after a redraw.
• Gracefully recover from a user moving twice on their move by choosing the first move (due to a buggy client implementing the protocol.) Eh, I hope that's the right philosophical approach, anyway :P.

[christianbundy]

Eh, I hope that's the right philosophical approach, anyway :P.

I think so, otherwise you'd be in a position where users could edit their moves after the fact!