Closed GoogleCodeExporter closed 9 years ago
Isn't this the same as issue 271 ?
Original comment by gbtami
on 20 Jan 2008 at 12:15
No. Premove is when you make a complete move (drag and drop the piece on a
square)
before your opponent makes his move so that when his move is made, your chess
client
makes the move on your behalf automatically.
What I'm talking about is the ability to start dragging a piece -- but not drop
it --
before your opponent makes his move. This apparently isn't possible yet with the
pychess board code.
Original comment by mattgatto
on 21 Jan 2008 at 12:56
Now i see the difference, thx.
Original comment by gbtami
on 21 Jan 2008 at 1:06
Original comment by gbtami
on 21 Jan 2008 at 1:07
If premove was implemented, this would follow automatically.
Some would suggest that this is less cheating according to chess rules, but as
I see
it, touching a piece while you are not to more, is just as much cheat as
putting it down.
However this is really easy to implement, only changing BoardControl.py, so
while
premove might take a few releases yet, this could potentially be in the first
Stauton
alphas.
Original comment by lobais
on 23 Jan 2008 at 7:23
I've got this working for the most part in the attached patch. The only
remaining
small issue with the patch is when you pre-drag and hover over a square with
your own
piece on it, wait for the opponent to capture there, and then, during the
opponent's
capture animation, you quickly drop your piece on the square to capture his
piece in
turn, an animation back to your pre-dragged piece's source square is run before
the
capture.
The patch also fixes issue 483.
Original comment by mattgatto
on 25 Jul 2009 at 3:21
Attachments:
Original comment by mattgatto
on 25 Jul 2009 at 3:23
Added in revision 1521.
Original comment by mattgatto
on 12 Sep 2009 at 3:06
Issue 622 has been merged into this issue.
Original comment by gbtami
on 29 Dec 2010 at 6:06
Original issue reported on code.google.com by
mattgatto
on 19 Jan 2008 at 9:09