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 546759 - Fail to recognize "#N/A" as error on cells with any formatting except "General"
Fail to recognize "#N/A" as error on cells with any formatting except "General"
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
git master
Other All
: Normal enhancement
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2008-08-07 10:00 UTC by Reggie Chan
Modified: 2008-08-26 20:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Reggie Chan 2008-08-07 10:00:50 UTC 
Steps to reproduce:
1. set A1's formatting to "mm/yy"
2. input "#N/A" (not necessary #N/A, other #XXX do not work as well) to A1

Expected result:
A1 = #N/A (of type error)

Actual result:
A1 = #N/A (of type text)
Comment 1 Jody Goldberg 2008-08-24 19:49:40 UTC 
Parsing errors is murky users are not supposed to be entering them manually for the most part, and should use the functions to generate them.  Beyond that do we want to compare against the builtin error codes before comparing with fmts ?
Comment 2 Morten Welinder 2008-08-25 00:32:41 UTC 
I think it would be pretty harmless to match against built-in errors
if the matching would otherwise fail.
Comment 3 Morten Welinder 2008-08-26 01:42:42 UTC 
We actually need this to work: someone can use paste-as-value to put
error values into cells.  Those values should, as a rule, survive F2+Enter.
Comment 4 Morten Welinder 2008-08-26 20:47:44 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.