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 125230 - using some time formats change the value
using some time formats change the value
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 125441 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-10-22 17:50 UTC by Ain Vagula
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ain Vagula 2003-10-22 17:50:08 UTC
Just take a new document. 
1. Pre-format cell(s) as 'Time' or 'Custom' with format code [h]:mm:ss 
2. Type 0:3:44 or 0:03:44 
3. After pressing enter, value changes to 0:03:43 
4. If we now change format to h:mm:ss (was [h]:mm:ss), cell shows right 
value, i.e 0:03:44 
 
We could replicate this with Gnumeric 1.2.0 on Debian and 1.2.1 on SuSE, 
also tried with different locale settings, always the same.
Comment 1 Jody Goldberg 2003-10-22 18:52:42 UTC
I can not replicate this.
Comment 2 Jody Goldberg 2003-10-22 21:24:32 UTC
Ray does this show up for you ?
Comment 3 Andreas J. Guelzow 2003-10-22 22:22:30 UTC
I can replicate this with current cvs.
Comment 4 Jody Goldberg 2003-10-23 02:34:10 UTC
so it's compiler or compiler flag specific.  The code for elapsed
hours looks like its already doing epsilon rounding.

Andreas could you have a look ?
Comment 5 Andreas J. Guelzow 2003-10-23 03:41:56 UTC
Since I can replicate the problem, I guess I don't have much choice
other than taking a look.  :-)
Comment 6 J.H.M. Dassen (Ray) 2003-10-23 07:29:33 UTC
It's reproducible for me as well. (Up to date sid system; gnumeric
1.2.1-3)
Comment 7 Jody Goldberg 2003-10-24 21:06:48 UTC
*** Bug 125441 has been marked as a duplicate of this bug. ***
Comment 8 Jody Goldberg 2003-10-24 21:07:45 UTC
I see.  Replication required an optimized build.
We needed to add epsilon before scaling.

fixed.