This catches me out nearly every time. If I drag a piece, but release it on the same square I picked it up from, the piece remains highlighted, and so moves to the next square I click, when I intended to move the piece already on that square. When this happens, in the lack of the undo facility I find myself having to reset the board and then start the sequence of moves I'm trying over again.
 
Clearly the intention was to give the user the choice of click-and-click or drag-and-drop to move pieces on the board. In the current implementation, if the mouse button is released in the same square it was pressed, the click-and-click interface is activated, regardless of whether it strayed from the original square in the interim.
 
This ought to change. I therefore propose an implementation where, if the piece leaves and then re-enters the square in the course of a drag-and-drop operation, it will detect that it was a drag-and-drop operation rather than simply clicking on a piece.
 
It need not actually leave the square - moving more than a set number of pixels or the button being held down for more than a set length of time could be caught as well.

I was noticing it in the analyze facility, hence the comment about resetting the board and starting the sequence of moves again. But I've noticed that the same quirk is in the move entry and if/then interfaces, along with another issue.
 
In if/then, if you try moving a piece by click-and-click, the piece moves but the interface otherwise doesn't acknowledge that a move has been entered. Hence if it happens on the if move then you can't enter the then move, and if it happens on the then move then you can't confirm it. You have to cancel and re-enter the if/then moves for it to work.

Posted by AdminBrian on AA:
> I am not quite sure of the problem you are having. You are saying
> that sometimes when you mean to click and drag you accidentally drop
> the piece on the starting square, thus mistakenly putting you into
> click and click mode, thus requiring you to reset to go back to click
> and drag mode?
 
It's not so much _accidentally_ dropping a piece as changing my mind about wanting to move that piece. But my point is that when I have dropped a piece in such a situation, I accidentally move the piece I dropped to another square I intended to move a piece _from_. So I have to reset to get back the piece that has been overwritten by the accidental move.

> It's not so much _accidentally_ dropping a piece as changing my mind
> about wanting to move that piece. But my point is that when I have
> dropped a piece in such a situation, I accidentally move the piece I
> dropped to another square I intended to move a piece _from_. So I
> have to reset to get back the piece that has been overwritten by the
> accidental move.
 
OK, I understand the issue you are reporting. I'll make a note of it, however, at this time it is hard to gauge the severity of the issue. We have not had other reports of the issue, and in making 30 or so corr moves a day for the last few weeks I have not experienced it myself. Obviously if more people report the problem in the future, we will make it more of a priority.