After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 628082 - unexpected default format
unexpected default format
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Main System
git master
Other All
: Normal normal
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-08-26 23:52 UTC by Andreas J. Guelzow
Modified: 2010-08-31 20:10 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Tentative patch (6.10 KB, patch)
2010-08-27 13:38 UTC, Morten Welinder 		none Details | Review

Description Andreas J. Guelzow 2010-08-26 23:52:29 UTC 
new gnumeric
enter 48:0:0 into A1
the cell displays 48:00:00

One should have expected to see 48:00:00. THis is obviously happening because the cell format is set to hh:mm:ss rather than [hh]:mm:ss. 

I always thought that this was happening to behave like XL. I just noticed that if you enter 48:0:0 into XL 2007 you get 48:00:00 and the format is [hh]:mm:ss.

Note that this is different from first entering 3:0:0 and then 48:0:0 into the same cell, since the 3:0:0 causes the cell to be set to format hh:mm:ss.
Comment 1 Morten Welinder 2010-08-27 12:29:17 UTC 
> new gnumeric
> enter 48:0:0 into A1
> the cell displays 48:00:00

You mean "displays 0:00:00".
Comment 2 Morten Welinder 2010-08-27 13:00:20 UTC 
I'll take this.  I see other problems in there.
Comment 3 Morten Welinder 2010-08-27 13:38:34 UTC 
Created attachment 168877 [details] [review]
Tentative patch

Please try this.  This is not a part of the code I really like messing
with too much.  In other words, having some kind of test suite for
number matching would be nice.
Comment 4 Andreas J. Guelzow 2010-08-27 17:52:04 UTC 
Comment on attachment 168877 [details] [review]
Tentative patch

This looks and behaves fine for me.
Comment 5 Morten Welinder 2010-08-31 20:10:44 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.