03 Dec 02
Russ!
When I put a piece in one position without touching the move buttom,
why is the move made?
I am trying to look at possible moves and the first get made!!!!!!
This has happened to me in several cases. I did not realize that until
I starated to pay attention to it.
Sincerely,
Harri / Luck
04 Dec 02
Originally posted by LuckHarri - I pointed this out a few months ago and Russ / Chrismo said
Russ!
When I put a piece in one position without touching the move buttom,
why is the move made?
I am trying to look at possible moves and the first get made!!!!!!
This has happened to me in several cases. I did not realize that until
I starated to pay attention to it.
Sincerely,
Harri / Luck
they'd work on it. It happens about once every 100 moves - so for me
quite a lot... 😉
It sometimes happens when I've tried out a few positions and at
others, as you've found, as soon as I've placed the piece.
It might be my imagination but it seems to happen most with
Queens...
I can confirm that you don't have to go anywhere near the move
button for this to happen. I'm trying to be more cautious about doing
too much experimenting with positions for this reason.
Rhymester (Andrew)
04 Dec 02
Originally posted by RussRuss - I can't 'make' it happen either. Would you be able to learn
I have tried to duplicate this, and I can't - this really needs fixing if
it
is a problem, so any help about when/where/why it happens would be
great.
-Russ
anything from a move that has been 'prematurely accepted' after the
event?
Rhymester
04 Dec 02
Originally posted by RussBut the position would be the same... it's just as though an invisible
I can't think why/how it would happen in the first place, so all I can do
is code in some preventitive stuff which checks boad position to what
is about to be submitted.
-Russ[/b]
finger has clicked the move button.
Anyway... on a similar subject. One thing that happens to me on a
frequent basis is catching the resign box rather than move button. On
my screen they're REALLY close together. I know that I get a second
chance but it's a bit of a pain. Moving it down a bit wouldn't be too
hard would it?
I've had games that my opponents have resigned in after one or two
moves and I've got a feeling that this might be the reason. I think
they must have been newbies and clicked on the accept screen by
mistake.
Rhymester
04 Dec 02
1 edit
Originally posted by RhymesterOk, sorry - you are quite right. I should learn to read. 😕 - I was
But the position would be the same... it's just as though an
invisible
finger has clicked the move button.
I've had games that my opponents have resigned in after one or two
moves and I've got a feeling that this might be the ...[text shortened]... ewbies and clicked on the accept screen by
mistake.
Rhymester
getting confused with something someone else reported a while back
which I could never reproduce.
-Russ
BTW Resign button - no problem moving that lower.
04 Dec 02
OK Russ: Game No: 108496 Move 60. Put my E pawn onto E5. Decided
to push my G pawn to G4 instead but as I made the second move the
screen moved on to the next game. Going back to the game I see
that the first move was accepted instead. Needless to say I didn't go
anywhere near the move button. Hope this helps.
Rhymester
04 Dec 02
it's just as though an invisiblethis might be a silly suggestion, but is there any keyboard key/key
finger has clicked the move button.
combination that would initiate the move, in the same way as people
used to post blank posts on the old forums by hitting return too
early... could the problem be cause by glancing or sticking keys?
(ie. as soon as a piece is moved the machine accepts the move code
from the keyboard even though the screen move button was never
touched - sorry, have a headache & wanted to mke sure I was being
clear)
04 Dec 02
Originally posted by belgianfreakNo... this happens without me going anywhere near the keyboard. It's
is there any keyboard key/key
combination that would initiate the move, in the same way as people
used to post blank posts on the old forums by hitting return too
early... could the problem be cause by glancing or sticking keys?
(ie. as soon as a piece is moved the machine accepts the move code
from the keyboard even though the screen move button was never
touched - sorry, have a headache & wanted to mke sure I was being
clear)
all done with the mouse. And my hands never leave my wrists...😉
Rhymester