Bug 262435 - Forty & Eight game unplayable due to misplacing of cards
Summary: Forty & Eight game unplayable due to misplacing of cards
Status: RESOLVED FIXED
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: 0.7.4
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Parker Coates
URL:
Keywords:
: 263241 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-07 18:09 UTC by Luis Silva
Modified: 2011-01-15 18:26 UTC (History)
3 users (show)

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 Luis Silva 2011-01-07 18:09:34 UTC
Version:           0.7.4 (using KDE 4.5.90) 
OS:                Linux

When playing a "Forty & Eight" game in kpat, the cards from the deck fly offscreen making the game unplayable.

Reproducible: Always

Steps to Reproduce:
Start kpat and try to play a "Forty & Eight" game. Click on the deck to get new cards at least twice.

Actual Results:  
Cards fly offscreen and are therefore impossible to access.

Expected Results:  
New cards should pile up next to the deck

OS: Linux (x86_64) release 2.6.37-12-generic
Compiler: cc
Comment 1 Parker Coates 2011-01-08 20:01:32 UTC
SVN commit 1212944 by coates:

Fix yet another issue with rightward and upward growing pile layouts.

BUG:262435

 M  +12 -5     kcardpile.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1212944
Comment 2 Parker Coates 2011-01-08 20:04:22 UTC
SVN commit 1212945 by coates:

Backport of commit 1212944.

Fix yet another issue with rightward and upward growing pile layouts.

CCBUG:262435


 M  +12 -5     kcardpile.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1212945
Comment 3 Myriam Schweingruber 2011-01-09 20:49:23 UTC
Will this fix make it into KDE 4.6 final?
Comment 4 Parker Coates 2011-01-10 14:46:50 UTC
It's been backported to the 4.6 branch, so yes, it should.
Comment 5 Parker Coates 2011-01-15 18:26:23 UTC
*** Bug 263241 has been marked as a duplicate of this bug. ***