Two errors with the Pairs application

[Karvjorm]

Again I found some errors when playing with the Pairs application.

The first one occured when I had the basic layout. I have found already some pairs and selected a not-selected coordinate. When picture under coordinate was shown, I started to move on mouse pointer and when it was hovering over another not-selected coordinate, picture suddenly showed though I had not clicked that coordinate. When I continued to move on mouse pointer, that picture was hidden again and after a while I was able to click another not-selected coordinate. I was just like application hinted that there was that kind of picture in that coordinate.

Another error occured when I started application in 8x8 layout and selected the first coordinate on the top-left corner. Next I selected coordinate at the bottom-right corner. They were not pairs but anyway, selection stayed and I could quite easily take a screenshot included here.

[Karvjorm]

Selection error in Pairs application

[Karvjorm]

In the session showed in the picture the right-bottom coordinate disappeared when I clicked some other coordinate, but the picture at left-top coordinate stayed. The next click did nothing but after that I could continue as usual, except that there was one odd pair pictures with one picture in pair.

[Karvjorm]

The next phase in faulty Pairs session.

[Karvjorm]

In syslog (/var/log/syslog) I was able to find the following kind error messages:

KERN: ps2: strange mouse data, x-delta 255, trying resync
KERN: ps2: strange moude data, x/y overflow, trying resync
KERN: ps2: bad mouse data, trying resync

Also, this continued and the first line above told sometimes about y-delta -126, x-delta -177, y-delta -255 etc. I'm using touchpad of my laptop as a mouse.

[Karvjorm]

Third phase after selecting new from the Peli menu

[Karvjorm]

The next error occured when I decided to stop and selected a new game from the "Peli" menu. The enclosed Pairs8x8Error3.png file shows that picture at the top-left coordinate did not disappear !

[Karvjorm]

Case break change, New game intializations, Style cleanups

[humdinger]

After applying your patch, the playing cards aren't turned on a click when starting another game after finishing the initial one, or you change the board size to advanced etc.

[Karvjorm]

Replying to humdinger:

After applying your patch, the playing cards aren't turned on a click when starting another game after finishing the initial one, or you change the board size to advanced etc.

Oops, I did no test it then... Can I delete this patch?

[pulkomandy]

I can't reproduce the problems here. Do they still happen?

[Karvjorm]

Yes, I recently got even new pictures about this bug, but I made a pgkman update for may Haiku installation after it and cannot boot that partition (with the picture files) any more.

[Karvjorm]

After the completed game one square is still hidden

[Karvjorm]

Lets find the pair of this square

[Karvjorm]

The pair should be here, shouldn't it

[Karvjorm]

What the ...! One pair is missing

[Karvjorm]

Phase 1: 3rd last one (the printed circuit board on the right) was clicked, but ...

[Karvjorm]

Phase 2: the 3rd one reverted after a delay to the orginal state. Not (fixed) visible even after the multiple clicks.

[Karvjorm]

I tried to add 2 more pictures that describe this error, but Trac is considering it as a spam :-(

[Karvjorm]

Phase 3: The 1st item of the last pair is selected.

[Karvjorm]

Phase 4: The last one was clicked.

[dsizzle]

I can't be sure if I'm seeing _all_ of the problems, but I can reproduce one issue 100% with these steps:

1. start Pairs
2. click on one card
3. Choose File->New game

the card you left exposed when the game was restarted will now behave oddly when clicked. If you click it to turn the card over, after a moment it'll flip itself back. Then if you click it again, it'll stay as a ? and not flip. If you click a few more times it'll flip over, and stay flipped no matter what other cards you click.

I am going to try to fix the issue.

[waddlesplash]

Fix merged in hrev55923.