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 85950 - number matching only checks the first format in a tuple
number matching only checks the first format in a tuple
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
git master
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 115728 167297 312215 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-19 16:31 UTC by Jason Mancini
Modified: 2005-09-05 03:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jason Mancini 2002-06-19 16:31:27 UTC 
Steps to reproduce

1) launch gnumeric
2) select a1:b1
3) click the "cash" format on the toolbar
4) enter =b1 into cell a1
5) tools->goal seek
6) set cell: a1
7) to value: 0
8) by changing cell: b1
9) click apply
10) bzzt: to value becomes "$-"!!
11) click apply:  "The value given in 'To Value:' is not valid."
Comment 1 Andreas J. Guelzow 2002-06-22 05:44:42 UTC 
At least in 1.1.x this does not seem to be a goal seek problem but a
general formatting problem. The cell A1, which has the value 0, is
formatted as $-. So is B1 if we enter there 0. These formats are then
carried into the goal seek tool and then fail to be scanned.

I have changed the topic to reflect this situation.
Comment 2 Jody Goldberg 2002-06-24 02:07:53 UTC 
The format is correct to become $-.  That is what it is supposed to do.
The bug is that the number match engine only matches against the 1st format in
a collection.  The $- is the 3rd.  This will be fixed when the new format
engine comes online.
Comment 3 Morten Welinder 2003-07-14 16:34:05 UTC 
*** Bug 115728 has been marked as a duplicate of this bug. ***
Comment 4 Morten Welinder 2005-02-14 18:45:24 UTC 
*** Bug 167297 has been marked as a duplicate of this bug. ***
Comment 5 Morten Welinder 2005-08-01 20:55:33 UTC 
*** Bug 312215 has been marked as a duplicate of this bug. ***
Comment 6 Jody Goldberg 2005-09-05 03:01:54 UTC 
Fixed for 1.5.90