| Summary: | >2-minutes timesteps are not correct | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | Frederik Schwarzer <schwarzer> |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | akarsh.simha |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Frederik Schwarzer
2008-02-06 16:30:22 UTC
You are right, the exact definition of the timestep changes at a particular timescale. It should be "10 min" though, not 2 min. For timesteps up to 10 min, time passes at a rate of "X per second". At 10 min and above, the context switches, and instead, every frame displayed is X later than the previous one. For example, when set to "10 min", you'll notice that the values of the seconds and single-minute digits do not change, and the ten-minute digit advances by one on each timestep. I know this is an inconsistency, but I think it's valuable to make this transition at some point when going to larger timesteps. For example, you can set the timestep to "1 day", point south at noon, and then start the clock. You will then be able to watch the Sun move up and down in the sky as the year progresses, illustrating the reason that we have seasons. You could not do that if the "1 day" timestep meant "make time pass at 1 day per second, showing many frames at random time intervals". I suppose the same effect could be achieved even if we did change the meaning of large timesteps, by pausing the clock and using the "change time by a single step" action (mapped to ">" and "<" in the default en_US layout). Unless there's good reasons for changing the current setup, I'm inclined to leave it as it is. I've CC'd the kstars-devel list in case other devs want to chime in. On 6 Feb 2008 15:30:23 -0000, Frederik Schwarzer <schwarzerf@gmail.com> wrote: [bugs.kde.org quoted mail] The best way to resolve this bug is to fix the what's this help for the time step spinbox which doesn't make this clear. We can't do this for KDE 4.2 because of the string freeze. This could be done after the string freeze is lifted around late January. Akarsh, can you please fix this issue in SVN Trunk? SVN commit 1016042 by asimha: Adding a tooltip to the Time Step box describing the behaviour of the time step in KStars. This is my solution to bug 157263. Please reopen if there's a better way of fixing this. CCMAIL: kstars-devel@kde.org BUG: 157263 M +4 -0 kstarsinit.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1016042 |