You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by bu...@apache.org on 2008/11/25 00:05:44 UTC
DO NOT REPLY [Bug 46280] Unexpected ContinueRecord in
RowRecordsAggregate when PivotTables are present
https://issues.apache.org/bugzilla/show_bug.cgi?id=46280
Josh Micich <jo...@gildedtree.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from Josh Micich <jo...@gildedtree.com> 2008-11-24 15:05:42 PST ---
Fix applied in svn r720318 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=720318 )
The logic inside RowRecordsAggregate was changed to allow for ContinueRecords
after any UnknownRecord.
The arrangement of PivotTable records in the worksheet stream is not discussed
in the OOO documentation. Brief investigation suggests that they come after
all of the row-block records of the current sheet (regardless of the actually
positioning of the pivot table(s) on the sheet).
However, Excel 2007 seems to put MSODRAWING(0x00EC) before the PivotTable
records, and this should have prevented this bug, since RowBlocksReader stops
at DrawingRecord.sid(0x00EC). I am assuming that the offending file does not
have an MSODRAWING record before the PivotTable records, so I added a fix in
RecordOrderer.isEndOfRowBlock(int) to make sure PivotTable records are not
included in the 'row blocks'.
My original assumption was that re-saving with Excel removed the offending
ContinueRecord. Now I am guessing that re-saving with Excel put the MSODRAWING
record in the right place.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org