| Summary: | Does not show hours | ||
|---|---|---|---|
| Product: | [Applications] knetwalk | Reporter: | Frederik Schwarzer <schwarzer> |
| Component: | general | Assignee: | Fela Winkelmolen <fela.kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aacid, kde-games-bugs, majewsky, oldherl, ped |
| Priority: | NOR | ||
| Version: | 3.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Frederik Schwarzer
2011-07-02 19:01:54 UTC
This is intentional, though:
m_gameClock = new KGameClock(this, KGameClock::MinSecOnly);
I am not sure if we should change that. The time stamp becomes unnnecessarily big then.
Opinions?
I'd vote WONTFIX. However, in a somehow related manner, it might be a good idea to pause the game after a few minutes inactivity to remedy the IMO more realistic case of hour-long games (a window left open accidentally). I would instead display "hour+" string when 3600+ seconds are detected, but this may add more problems with localization (the English "hour+" would almost fit into mm:ss space). Maybe infinity symbol would work even better (in this context to be understood as 'beyond game limits'), and normalize the value to 3600 for every such score. This also affects kmines: https://bugs.kde.org/show_bug.cgi?id=448364 I propose to have a "flexible" format or a "long minutes" format, so that the time string extends when it is greater than 1 hour. ``` Format Example1 Example2 --------------------------------------- HourMinSec 00:04:05 01:02:03 MinSecOnly 04:05 02:03 FlexibleHourMinSec 04:05 01:02:03 LongMinSec 04:05 62:03 ``` Using the "long minutes" format, a time period longer than 60 minutes (or even a day) could be represented, whilethe the string representation for ordinary short time periods are kept the same and easy to read. |