Issue 18294 - Incorrect behaviour of conditional text, hidden text, and hidden paragraph fields
Summary: Incorrect behaviour of conditional text, hidden text, and hidden paragraph fi...
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC3
Hardware: PC Windows XP
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-08-16 23:05 UTC by martinwhitaker
Modified: 2013-08-07 14:41 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Spreadsheet used as data source (5.53 KB, application/octet-stream)
2003-08-16 23:06 UTC, martinwhitaker
no flags Details
Document demonstrating bug (5.40 KB, application/octet-stream)
2003-08-16 23:07 UTC, martinwhitaker
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description martinwhitaker 2003-08-16 23:05:21 UTC
I have created as a sample data source a small spreadsheet, consisting of two
sheets, each containing 6 rows by 2 columns. This gives me two data source
tables, each with 6 records of 2 columns.

I have inserted this data as fields into a writer document, with each row of the
spreadsheet on a separate line of the document. To the first 3 rows taken from
each table, I have added conditional text, hidden text, and hidden paragraph
fields based on the 1st column of the table, and to the last 3 rows taken from
each table, I have added conditional text, hidden text, and hidden paragraph
fields based on the 2nd column of the table.

If I open the document, then press F9 to update all fields, the conditional
text, hidden text, and hidden paragraph fields based on the 1st column of a
table behave correctly, but those based on the second column behave as if the
condition always evaluates to false.

If I then select all rows of the 1st data source table and click on the "data to
fields" button in the data source view, all the conditional text, hidden text,
and hidden paragraph fields based on the 2nd data source table behave as if the
condition always evaluates to false. Pressing F9 restores the original behaviour.

If I then select all rows of the 2nd data source table and click on the "data to
fields" button in the data source view, the conditional text, hidden text, and
hidden paragraph fields based on the 1st data source table behave as if the
condition always evaluates to false. Pressing F9 does not restore the original
behaviour.

If I then go back and select all rows of the 1st data source table and click on
the "data to fields" button in the data source view, the conditional text,
hidden text, and hidden paragraph fields based on the 2nd data source table
behave as if the condition always evaluates to false, but this time pressing F9
does not restore the original behaviour.

If I disconnect from the data source, then press F9, all the conditional text,
hidden text, and hidden paragraph fields behave as if the condition always
evaluates to false.

So, to summarise, there are two (potentially related) bugs here - the
conditional fields based on the second column of a table never work correctly,
and conditional field evaluation is disrupted by updating the data source fields
used by the evaluation.

I also see this bug in OOo 1.0.2 running on Linux, although in that case
pressing F9 can make fields evaluate to true when they should evaluate to false,
and successive presses of F9 change the behaviour.

This bug may be related to issue 15100, although that bug is reported as only
present in OOo 1.1x, not in OOo 1.0.x.
Comment 1 martinwhitaker 2003-08-16 23:06:42 UTC
Created attachment 8504 [details]
Spreadsheet used as data source
Comment 2 martinwhitaker 2003-08-16 23:07:27 UTC
Created attachment 8505 [details]
Document demonstrating bug
Comment 3 h.ilter 2003-08-22 13:40:53 UTC
Reassigned to ES
Comment 4 phillg 2003-09-11 13:22:20 UTC
The problem here is the fact that the second column is numbers and not
text.  If you change the second column to read {one, two...} and
update the hidden paragraphs then everything works as expected.

The correct way of writing conditions for numbers is:
ColumnB == 4
rather than 
ColumnB == "4"

There is also a linked problem with fields with hyphens in their name,
they require quotes around their name, e.g. not("E-Mail") is needed
while not(E_Mail) works fine.

I think there needs to have the help component updated, I'll try
writing it this afternoon.
Comment 5 phillg 2003-09-11 15:54:39 UTC
See issue 19454 for the proposed change to the Help text
Comment 6 martinwhitaker 2003-09-12 00:39:02 UTC
OK, I agree that the first bug I refer to is my mistake.
Unfortunately, this only came up as part of my effort to create a
simple test case to demonstrate the second bug I refer to - which
still exists when I change from numbers to words.

To recap, if you update the fields from one data source table (using
the "data to fields" button), it causes the conditional text, hidden
text, and hidden paragraph fields based on another data source table
to evaluate incorrectly.

There is at least a workaround for this bug - if you exit OOo then
restart, reload the document, and press F9, all fields evaluate
correctly - until you next do an update from the data source.
Comment 7 stx123 2003-09-12 15:12:15 UTC
Hi, please let developers set the target milestones after 
confirmation and evaluation of issues.
Thanks, Stefan
Comment 8 martinwhitaker 2003-09-12 23:48:00 UTC
Sorry, I didn't notice that the target milestone had been changed when
I reopened the bug.
Comment 9 utomo99 2004-04-21 08:20:51 UTC
Please try using the latest OpenOffice 1.1.1 or maybe 1.1.2rc , you can 
download it from http://download.openoffice.org/1.1.1/index.html
many bug fixes and enhancements since your version and 1.1.1 . If the problem 
still happend in 1.1.1 please report back. 
It maybe not yet solve your Issue, but it worth to try.
Comment 10 martinwhitaker 2004-04-22 00:31:37 UTC
I went to the trouble of isolating this bug in a small test case and documenting
it - is it too much to ask for someone else to test and confirm it?

Anyway, I have just downloaded 1.1.2rc, and the bug is still present.
Comment 11 Rainer Bielefeld 2004-05-13 17:49:32 UTC
Hi martinwhitaker,

you are right, it is a dissatisfactory situation that this issue still is
unconfirmed after that long time. To get some progress for your problem, I will
close this issue and ask you to reopen a new one. I promise that I will check
and - if possible - confirm the bug immediately (for that please set me CC for
your new issue, so that I will get information.

I have 3 reasons to close this issue:

1. I have too less knowledge concerning all that special text formatting to
confirm or to disprove your results with the actual testcase (and no other one
seems to be interested to confirm your results).

2. Here has to be too much discussion without any result and some hints that
there was a mistake in your testcase.

3. We are discussing more than 1 problem here in the issue.

For the new issue please heed:

1. only 1 formatting problem (only "hidden text", not also "hidden paragraph")
in each issue.

Please create a new testkit (based on the one you attached here) which considers
the workaround hints.

Please give a very detailled step by step instruction, so that even I will
understand it ;-)
Not: "Do your own tests and you will see that that does not work proper ..."
but: "Hidden Text 1 contains the condition '...A1=="xyz"'. Because  ...A1 is not
"xyz", the text will not be hidden. Change ...A1 to "xyz" save both files and
reopen 'document'. " And so on, so that a philistine like me will be able to
reproduce all your results, because I only have to follow your instructions
keystroke by keystroke.

I hope you will agree with my proposal - so we will get a result, soon.

CU

Rainer
Comment 12 eric.savary 2004-06-24 15:23:02 UTC
I agree with your analyze of this issue.
Let's start from the begining: precisly and concisly!