Issue 17575 - bad cell formats e.g. >2 conditionals rejected w/o feedback
Summary: bad cell formats e.g. >2 conditionals rejected w/o feedback
Alias: None
Product: Calc
Classification: Application
Component: formatting (show other issues)
Version: OOo 1.1 RC2
Hardware: PC Windows XP
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa, rfe_eval_ok
Depends on:
Reported: 2003-07-29 16:07 UTC by Unknown
Modified: 2013-08-07 15:12 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-07-29 16:07:11 UTC
Certain custom format codes are not accepted, i.e. they simply don't change the
original format without any notification.

This seems to happen always if more than two conditionals are in the format, e.g.:

Comment 1 pmartel60 2003-08-02 02:58:23 UTC
I had the following problems reproducing this issue on 1.1 RC2:
The example format given: "[=0]0;[=1]0;[=2]0;" is NOT accepted
by the Format Cells dialog -- it complains about the third conditional.
This behavior is similar (and slightly clearer) than that in Office XP.
Even if it DID accept this case, how could you tell it worked? 
You are instructing it to use the same format for 0, 1, and 2 as it
normally would.
If you can attach a sample spreadsheet that shows the issue or give 
step-by-step instructions for reproducing this issue in a blank
spreadsheet, you can re-open this issue. You might want to reconfirm
what release you are using, as well.
One could argue that support for arbitrary chains of conditionals
would be useful, but that would be more of an enhancement request.
Even so, as it stands, this looks like a dead issue.
Comment 2 Unknown 2003-08-02 12:35:07 UTC
It is still like I wrote.

I'm using 1.1 RC2 on WinXP as stated above and I still DO NOT get any
error message when changing a format from anything (e.g. 'General'
from a new empty spreadsheet) to anything with three conditionals in it. 


was just an example, boiled down to the most simple form. The same
happens also for 


or anything else I have tried, also with really complex formats like

[>1]"(32 µM, n = "0", ";[=1]"(32 µM, n = "0") ";[=0];General

This is NOT an enhancement request as I could live with only two
conditionals. The problem is the missing notification. If you don't
check the format again then have no clue that it hasn't been accepted.

Additionally I haven't read about a two-conditionals-limitation, so I
guess it would be possible when accepted.
Comment 3 Unknown 2003-08-02 13:13:47 UTC
Here is a detailed procedure how to confirm this bug.

- open a new OO Spreadsheet document
- choose Format::Cells to open the 'Format cells' window
- change the 'Format code' from 'General' to '[=1]0;[=2]0.0;[=3]0.00;'
- click OK
- no error message or notification appears!
- choose Format::Cells to open the 'Format cells' window again
- the 'Format code' is still 'General'!
Comment 4 pmartel60 2003-08-02 13:34:25 UTC
My bad. Thanks for your patience.
I was hitting the "check" button each time to get the feedback
and not noticing that entering a bad format and just hitting OK silently 
rejects three-conditional and other invalid formats.
This issue is with the behavior of the OK button in the Format Cells
dialog. When it fails a check on any new User-defined formula (i.e. 
whenever the check button is enabled), it should return the user to the
dialog until the formula is valid (or the user hits the Cancel formula 
or Cancel dialog button).
Currently, it silently backs out (cancels) any invalid format changes.
Comment 5 oc 2003-08-05 11:31:37 UTC
This feature works as specified. If you click on the ADD button, the
wrong part of the formatcode gets selected. I agree that it would be
nice to inform the user about the mistake by a messagebox or something
else to minimize confusion. So I forward this issue as enhancement
Comment 6 bettina.haberer 2004-01-29 19:59:04 UTC
At the validation of the code the bad content is recognized as such and thus
removed - but unfortunately not visible for the user.
This issue is considered for OO.o later.
Comment 7 bettina.haberer 2004-01-29 20:00:27 UTC
'not visible', I mean without providing feedback for the user.
Comment 8 bettina.haberer 2010-05-21 15:01:40 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".