Menu
▾
▴
#67 Guessmove activates unexpectedly
A tricky test-case: start ChessX and without *ever* passing the cursor on the lower half of the chessboard (so that guessmove never highlights any square):
1. open a database and wait until it loads
2. move the cursor onto a black knight and leave it there for a while
3. move the cursor upwards, away from the chessboard
4. go to GameList window without passing on the chessboard again (including the grey region that surrounds it)
5. click on a game in GameList
5. browse the game with the right arrow key
You should get suggestions for knight's moves at black's turn.
This is not an uncommon situation, because the user often operates on the region pertaining to the chessboard (e.g. to access the menu). Furthermore, in some cases the piece involved (e.g. a rook) is blocked at the beginning of the game and sometimes for a long time, so that the highlight comes totally unexpected after several moves. Finally, I can reproduce it also for white pieces blocked in the starting position, for instance for the Ra1.
Deactivating guessmove any time the cursor is not within the chessboard region should be sufficient to solve the problem.
Logged In: YES
user_id=1713178
Originator: NO
Can't reproduce this Bruno. Perhaps its only a windows thing. Mind you I have
my own version:
1. Put mouse over black knight
2. Do Alt-tab to switch to a different program.
3. Move mouse off screen and do alt-tab back to ChessX.
4. arrow-keying through game shows guess-move is still active.
I don't think there is a way to get a signal from Qt that lets us know about
such situations. At the end of the day we may just have to accept this.
But i'll give another look through the Qt Docs, before closing this bug.
Logged In: YES
user_id=1728395
Originator: YES
Right, i have installed ChessX on a Ubuntu machine and it doesn't show up. It looks like a Windows thing.
I had some doubts following your 4 steps, but i think i understood the sense. Only, i didn't put the cursor on a black knight, but on a piece of the color that had to move, so that guessmove highlighted a couple of squares. Yeah, you have a behavior similar to the one i am reporting. Guessmove keeps reproposing when it shouldn't.
As a workaround, isn't it possible to deactivate chessmove at every key pressing and reactivate it when the cursor is moved again? Won't solve everything, but maybe can help. I apologize in advance if this doesn't make sense for a reason i don't see.
Finally, if we have to live with this, we will, of course. Only, i would suggest in general to leave the reports open as long as the bugs are still present. First, it probably avoids people to report over and over again the same misbehavior. And secondly, this might be a challenge for people to go and take a look at the code. In any case, i think nobody ever judges the quality of a piece of software from the number of bug reports that are still open.
The bug is solved and I am totally happy with it!