Celestia Forums

Celestia 1.3.1 pre 9, Windows ME, GeForce2 MX 200 32 MB, Spanish (Spain) international settings.

"Set time" dialog behaves strangely: I can set hours only, OR minutes only, OR seconds only. If I want to set two or three of them, I must close dialog and re-open it.

First time I click on time, I can select hours, for example, and increase or decrease them, but when I click again on minutes, entire time indicator is selected, and by using the arrows I still change hours. It's useless manually selecting minutes to alter them.

I've changed to USA regional settings, Windows 2000 and Intel 82815 4MB Graphics Controller and the same behaviour occurs.

Date indicator works well, however.

Out of curiosity, is the time value separator the ":" character, or some other character?

I'm seeing the same problem.
(the second click, even though delayed, acts as if I'd double-clicked the entire time text field)
After a third click, I can edit any or all of the h:m:s fields, but only the last one that I edited gets changed when I select the [ok] button.

Another related problem is that when I change the seconds field, it sets the time of the initial "set time" menu selection, not the time when I select [ok]. As a result, the seconds of the time immediately shown by Celestia may be many seconds after the time that was input.

In other words, what I see happening is consistant with the following sequence of events: 1) I select "set time", 2) Celestia's clock freezes, 3) I set the seconds, 4) I select OK, 5) Celestia sets the seconds to the value I specified, 6) Celestia updates the time to allow for the period it was frozen, 7( Celestia time progresses. I'd expect steps 5 and 6 to be reversed or for step 6 to be eliminated entirely.

I see both of these problems with Celestia v1.3.1pre3. And v1.3.0final. And v1.2.5final. And v1.2.4final. (v1.2.4 final seems slightly different: the hours changed but not minutes or seconds, although seconds was the last thing I changed before selecting OK.)

I'm starting to wonder if this is caused by a recent Windows "critical system patch" rather than Celestia, since Celestia uses time input routines provided by Windows. I don't remember it acting this way before.

System:
256MB 500MHz P3, U.S. English Windows XP Pro, SP1 with current patches
128MB GF4 Ti4200, Detonator 44.03 whql, OpenGL 1.4.0
various versions of Celestia

Just did some tests on my system ... 1.3.1 pre9, Dell/Intel P4, XP Pro SP1 English all patches/updates.

I can confirm the mouse problems. There are a couple of work-arounds I can suggest until it's fixed, if even possible to "fix" since it's supposed to be a MS routine...

1) Click where you want to start, then use the left and right cursor arrow keys to move between time fields and use the up and down arrow keys to change the value.

2) When using the mouse, click, set value, click the DATE field, clik next time field to update, click the DATE field, click next time field, etc. until you click OK.

These both seemed to work for me.

Regarding Selden's report of the Celestia time stopping when you select Set Time ... actually Celestia "Freezes" when you select *any* menu item from the menu bar, and continues when you are done. For example, if you select "File", the Celestia time freezes.

I can also confirm his observation that after setting a new time, the seconds and minutes that Celestia was "frozen" are added to the time you set.

-Don G.

Time value separator is ":" in my system.

I don't think the problem to be related with a "recent" MS system patch, since my Windows ME remains "unpatched" long ago. My other system (W2000 at work) shows the same behaviour after being fully updated/patched in Windows Update site.

Nice workarounds, Don. They work fine.

Regarding time addition after setting time, I find useful to freeze time (Space) BEFORE opening dialog to prevent it. That way Celestia time at exit is almost exact (one second below value set).

Pollux wrote:Regarding time addition after setting time, I find useful to freeze time (Space) BEFORE opening dialog to prevent it. That way Celestia time at exit is almost exact (one second below value set).

Great idea Pollux, thanks!