Bug 146008 - kpatience always starts a new game
Summary: kpatience always starts a new game
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdegames
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-24 18:03 UTC by Vladimir Mencl
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-01-24 18:17:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Vladimir Mencl 2005-01-24 18:03:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20041020

Description of problem:
kpatience always starts a new game.

If is not possible to keep a good score and get some work done.

After I win a game, I cannot immediately quit - kpatience
automatically starts a new game.

When I quit this just-started game, it counts towards the lost games
in the Game|Statistics window.

There should be an explicit command to start a new game, instead of
starting a new game automatically.

I have observed this behavior in the Freecell game type - but it
apparently applies to other game types as well.

Version-Release number of selected component (if applicable):
kdegames-3.3.1-1

How reproducible:
Always

Steps to Reproduce:
1. Start kpatience 
2. Win a game
3. I confirm the "You have won" dialog.
    

Actual Results:  Kpatience starts a new game.

Expected Results:  Kde shows a blank board, and starts a new game only
after I select to.

Additional info:

The proposed change (starting a new game only upon explicit request)
should apply also to starting kpatience (so that I can immediately
quit without having a game counted as lost) and switching game types.

Comment 1 Than Ngo 2005-01-24 18:17:35 UTC
for new feature in next KDE release, could you please add it to
bugs.kde.org. Thanks


Note You need to log in before you can comment on or make changes to this bug.