d23fa8e8a75f1a3744b7cc54c92ee4d2ddadf08e
1. Make sure a tile or piecen submitted is submitted by the current turn holder. 2. Wait to end the turn until after we've received the elementAdded notification for piecen placement and done the scoring. This ensures that all events that need to be dispatched before the turn ends are dispatched and that piecen removal is completed before we end the game and potentially do more scoring. 3. When scoring a tile, always use an array that we can modify during the scoring process to ensure that we don't score a claim group twice by virtue of it being completed by a tile with two of the same feature, both of which are linked into the same claim group. By removing piecens from the array immediately, we can tell that we scored a claim group the first time because the piecens belonging to the claim group will have been removed from the local array whereas they would not yet have been removed from the distributed set by virtue of the element removed events not yet having been dispatched. Distributed programming is tricky. git-svn-id: https://samskivert.googlecode.com/svn/trunk@437 6335cc39-0255-0410-8fd6-9bcaacd3b74c
Description
Samskivert Library
Languages
Java
96.5%
Shell
2.2%
HTML
1.3%