Bug 233776 - time shouldn't be resetted after game is won
Summary: time shouldn't be resetted after game is won
Status: RESOLVED DUPLICATE of bug 199844
Alias: None
Product: kmahjongg
Classification: Applications
Component: general (other bugs)
Version First Reported In: 0.8
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Mauricio Piacentini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-08 22:09 UTC by Toralf Förster
Modified: 2010-04-19 22:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Toralf Förster 2010-04-08 22:09:16 UTC 
Version:           0.8 (using 4.4.2 (KDE 4.4.2), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.34-rc3-00406-gcf90bfe

It would be nice if the time wouldn't restart with 0 even if the used time was too long.
Comment 1 Frederik Schwarzer 2010-04-19 17:55:38 UTC 
How should it be then? I do not see your vision. Can you elaborate a bit, please? :)
Comment 2 Toralf Förster 2010-04-19 18:45:54 UTC 
(In reply to comment #1)
> How should it be then? I do not see your vision. Can you elaborate a bit,
> please? :)
Oh - of course.

I'd prefer to hold that value to have a chance to compare it with the stored high scores :-)
Comment 3 Frederik Schwarzer 2010-04-19 20:33:37 UTC 
Ah ok. So it is basically the same request as: https://bugs.kde.org/show_bug.cgi?id=199844 ?

"Stop (not reset) the timer when the game ends"?
Comment 4 Toralf Förster 2010-04-19 22:35:21 UTC 
(In reply to comment #3)
> Ah ok. So it is basically the same request as:
> https://bugs.kde.org/show_bug.cgi?id=199844 ?
> 
> "Stop (not reset) the timer when the game ends"?

Yep - goes into the same direction.
Comment 5 Frederik Schwarzer 2010-04-19 22:41:15 UTC 
Ok, then I will marke this as duplicate and explain in the other report what is wanted. Thanks for your report.

*** This bug has been marked as a duplicate of bug 199844 ***