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 671850 - About logic operation "If ... Then ... Else ..."
About logic operation "If ... Then ... Else ..."
Status: RESOLVED DUPLICATE of bug 671632
Product: Gnumeric
Classification: Applications
Component: General
1.10.x
Other Windows
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2012-03-11 21:29 UTC by José Carlos Fernandes Rodrigues
Modified: 2012-03-11 21:36 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description José Carlos Fernandes Rodrigues 2012-03-11 21:29:42 UTC
I am writing a text for young people and adults about spreadsheets.

From an exercise proposed in the text, students are making contact with the "logical operation":

          If [condition] Then [Decision1] Else [Decision2]

This "action" is not working in some cells [not all].

For example, entered in cell  B5  was the "formula"  "=-19,6+23,9" (without the quotes) in cell  D5  type the numeric value was  4.3,  was entered in cell  E5  the formula:

                "=if($D5=B5;1;-0.5) "(without the quotes),

but the value that Gnumeric put in that cell is "-0,5"  when it should be "1".

This occurs in other cells and other cells is the result expected.

This panilha was tested in Excel and BrOffice and ran to the satisfaction.

Attached is a worksheet named "Avaliacao_final.gnumeric"

Thanks for your attention
Comment 1 Andreas J. Guelzow 2012-03-11 21:36:27 UTC
Did you read the explanation of this in your previous bug report #671632? Refiling the exactly same report at best causes annoyance among the developers. The value =-19,6+23,9 is simply not the same as 4.3 when the finite binary representation is taken into account.

This particular bug has already been reported into our bug tracking system.

*** This bug has been marked as a duplicate of bug 671632 ***