On 06/24/09 05:00, Xu Ming Wang wrote:
- The data in the Quantify screenshot looks strange. For any larger
calculation, screen output (OutputDevice::DrawLine) shouldn't play a
significant role.
It maybe relate to Quantify environment - drawing is very slow.
Actually, ScAttrArray::ApplyBlockFrame is a low performance function.
If the output table about 10000 rows, ScDPOutput::Output() used 8-10
seconds in our test environment.
Current solution, to data area in the table:
Case 1: all cells need set border, then setting block frame border
only once is ok.
Case 2: otherwise, set block frame border like this
Applying the frames takes some time in a large output table, that's right.
- "Data Source buffer" sounds interesting. Now it would of course be
helpful to see the actual code changes for it.
It is something like Excel's PivotCache, and better to save it in the
document file.
If that, we need the approval of the ODF format proposal relate it.
OOo 3.x has a cache (ScDPCacheTable), but it isn't saved, and the
results are still created using ScDPItemData. We'll have to see how we
can put these things together. Also, you're right, we'll have to clarify
the file format handling.
- The allocation for all members (B1,B2,B3) is what issue 55266 is
about. In the "Solution Description" section, there's only the heading.
Do you have a solution for that?
I have a solution in LateInitFrom. To row data, only new
ScDPResultMember when find it.
Excellent. I had something like that in mind for issue 55266, but never
found the time to actually try it.
All three changes you mention still seem to be valid and useful for 3.x.
How big are the individual changes, is it possible to extract them, so
we can try to update them to the 3.x code base?
Niklas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
