Bug 102954 - getting into broken state when moving card while autodrop in Freecell is enabled
Summary: getting into broken state when moving card while autodrop in Freecell is enabled
Status: RESOLVED DUPLICATE of bug 56637
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-31 18:56 UTC by schulte
Modified: 2005-04-01 18:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description schulte 2005-03-31 18:56:27 UTC
Version:           2.2.1 (using KDE KDE 3.3.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

This bug was first discovered by my son Tim - it's one of these bugs that will most probably only be discovered by children:

If you try hard, you will sometimes have luck to pick (left mouse) up a card while kpat is automatically dropping the rest (don't know if this is necessary) cards. I picked up one card that is to be moved to the sorted staples on the right, moved it onto the staples but didn't release the left mouse button. Then (before all cards are sorted in???) I move back the picked card into it's original row where it can be placed again. Then all cards up to the kings are placed on the right staples but not the card I picked up and moved back. You can continue playing with this card (moving it around). For a picture of the situation please take a look onto http://data.guug.de/kpat.error.png (where I picked up the 5 of hearts).

Sorry for this rather incomplete description, but it was hard to reproduce the problem at all.

Greetings and thanks,

Martin
Comment 1 Inge Wallin 2005-03-31 23:49:50 UTC
Hi Martin,

Thank you for the bug report. As unlikely as it may seem, this bug was actually previously discovered.  Look for instance at bug 56637 which describes the same phenomenon. 

*** This bug has been marked as a duplicate of 56637 ***
Comment 2 schulte 2005-04-01 18:14:02 UTC
Hi Inge!

> Thank you for the bug report. As unlikely as it may seem, this bug was
> actually previously discovered.  Look for instance at bug 56637 which
> describes the same phenomenon.


Oh yes, now I see it... I looked through the other reports, but I didn't see 
that this is mine...

Greetings,

Martin