After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 164638 - Aisleriot click-to-move allows invalid moves
Aisleriot click-to-move allows invalid moves
Status: RESOLVED FIXED
Product: gnome-games-superseded
Classification: Deprecated
Component: general
2.9.x
Other Linux
: Normal normal
: ---
Assigned To: Rosanna Yuen
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2005-01-19 22:30 UTC by Josselin Mouette
Modified: 2012-01-31 23:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Josselin Mouette 2005-01-19 22:30:56 UTC
[ forwarded from http://bugs.debian.org/268734 - still reproducible with 2.8.2 ]

http://people.debian.org/~jbailey/badspider.png shows a copy of me
picking up and moving a suit that I should really not be permitted to
move.

The trick to picking up the cards seems to be in click-to-move mode
where you click just above the line of the card right in the middle.

I can also reproduce this in the regular spider game, but I cannot
reproduce this in Freecell.
Comment 1 Richard Hoelscher 2005-01-20 03:18:59 UTC
Actually, seems it's triggered by clicking down on a valid card while the
release happens on the cards above it.
Comment 2 Richard Hoelscher 2005-01-20 03:28:58 UTC
Looks like it applies to all of aisleriot. (Including Freecell.)
Comment 3 Callum McKenzie 2005-01-23 06:14:56 UTC
Yes, it applies to all of aisleriot. The truth is I have known about it for
three months, but have avoided doing anything about it because the problem is in
a piece of code which scares me. Because of the fragility of the code involved
this may be a post-2.10 fix if it involves too much fiddling.
Comment 4 Callum McKenzie 2005-02-10 09:53:50 UTC
Fixed in CVS by moving the check for a valid sequence further out in the code.
It turns out that the double click code had a fall-back for click-to-move to
allow a quick pickup when double-click didn't make sense. Unfortunately it
didn't check that the sequence was a valid one before doing so. The code is now
a bit cleaner.
Comment 5 Robert Ancell 2012-01-31 23:32:03 UTC
This bug is being reassigned to the "general" component so we can close the aisleriot bugzilla component.  Apologies for the mass email!