Issue 104418 - DataPilot: field member popup window does not show members correctly
Summary: DataPilot: field member popup window does not show members correctly
Alias: None
Product: Calc
Classification: Application
Component: ui (show other issues)
Version: DEV300m50
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-08-21 20:39 UTC by kyoshida
Modified: 2013-07-30 02:40 UTC (History)
2 users (show)

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

test document (9.17 KB, application/vnd.oasis.opendocument.spreadsheet)
2009-08-21 20:40 UTC, kyoshida
no flags Details
a little simpler example (7.14 KB, application/vnd.oasis.opendocument.spreadsheet)
2009-08-21 21:34 UTC, kyoshida
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description kyoshida 2009-08-21 20:39:34 UTC
This bug is relevant only to koheidatapilot03 cws.

The field member popup window (still in development) lists field members
incorrectly when the field consists of numbers, dates, or other values that use
special number format.  I will attach a test document that I received from Xu
Ming Wang of IBM.
Comment 1 kyoshida 2009-08-21 20:40:20 UTC
Created attachment 64315 [details]
test document
Comment 2 kyoshida 2009-08-21 20:40:52 UTC
accepted.  I'll try to fix this in koheidatapilot03.
Comment 3 kyoshida 2009-08-21 21:34:10 UTC
Created attachment 64316 [details]
a little simpler example
Comment 4 kyoshida 2009-08-21 21:40:42 UTC
Actually this has nothing to do with the new popup window; the problem is

When a field contains fractions, such as 1.1, 1.2, 1.3, ... but no decimal
places are shown (as in fraction_members.ods test document), datapilot table
displays the numbers as 1, 1, 1, 1, 1, ...., which is expected.

But when you filter by, say, 1.1, via popup, it filters correctly, but the
second time you launch the popup, member visibility is evaluated incorrectly,
and the popup ends up listing all the '1's as invisible.

And because this problem is a pre-existing condition, you can see the same
problem in the existing field options dialog, under Hide items list.
Comment 5 kyoshida 2009-08-21 22:40:21 UTC
removed this from koheidatapilot03.  This is a pre-existing bug & has nothing to
do with the new field popup window.  We should tackle this separately.
Comment 6 kyoshida 2009-08-21 22:54:07 UTC
This requires a file format change in ODF, since the visibility data is stored as 

    <table:data-pilot-member table:name="1" table:display="false"

where the name is clearly stored as "1".  To fix this, we need to store the
index of a member, instead of its name.
Comment 7 Rob Weir 2013-07-30 02:40:30 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.