summaryrefslogtreecommitdiffstats
path: root/sc/inc/dpresfilter.hxx
Commit message (Collapse)AuthorAgeFilesLines
* boost::unordered_map->std::unordered_mapCaolán McNamara2015-01-031-2/+2
| | | | Change-Id: I2c65709cda6f10810452dfb8aa1a247cb3a5564f
* remove whitespaceMarkus Mohrhard2014-06-251-1/+0
| | | | Change-Id: Ib15413e73409cc33de01fa92a47b9d1237cfc4b2
* fixincludeguards.sh: scThomas Arnhold2014-04-191-2/+2
| | | | sorry, huge one...
* fdo#72645: Allow GETPIVOTDATA to get result from leaf node of result tree.Kohei Yoshida2014-01-071-0/+12
| | | | Change-Id: I0fc1fd069440ed6fee378fc2dfd2ed761afbdeab
* fdo#66655: Get GETPIVOTDATA to work again.Kohei Yoshida2013-07-111-2/+2
| | | | | | | | | | | | 1) Compare data field name as it is displayed in the table output. 2) In the result tree, store field member names as strings as displayed in the table output, instead of as ScDPItemData. GETPIVOTDATA operates on displayed cell values and do textural comparison. There is no use storing ScDPItemData which screws up value lookup in the result tree. Change-Id: I31bc03a6800f4fadf2ba1180d1958354d43e8a07
* Rename to ScDPResultTree.Kohei Yoshida2013-04-191-5/+5
| | | | | | It *is* a result tree. Let's call it that. Change-Id: Ie8f3e4c4f6e54fd84d79b80ac98c0be0b0cc42d4
* Remove debug statements..Kohei Yoshida2013-04-191-11/+1
| | | | Change-Id: I10e0ef90ea7bfd92b46a54dc3d3feff90e50f724
* Retrieve the result value for GETPIVOTDATA for real (finally!)Kohei Yoshida2013-04-191-3/+8
| | | | Change-Id: I68f4fdab667d86e79225a77964ed90373b391d08
* More progress. Getting more clue, but still not out of the dark yet.Kohei Yoshida2013-04-191-3/+13
| | | | Change-Id: I0467cd95e2c6f2f353333b24e1aba737d99e5c20
* Add some more notes to make it easier to pick up on this for my next visit.Kohei Yoshida2013-04-191-0/+15
| | | | | | Looks like I have to put this on the shelf once again... Change-Id: I6288d019170278e484befaac3ee57cea24a69c0e
* fdo#60300: Work-in-progress change to rework pivot table core.Kohei Yoshida2013-04-191-0/+115
The idea is to avoid parsing the pivot table sheet output in order to calculate GETPIVOTDATA. The table outout is configurable, and it will only be more configurable in the future. The gist of my rework is to calcualte the result of GETPIVOTDATA with the internl result tree alone. Also, the same result tree can be used for drill down too, which also currently parses the table output, therefore subject to the same limitation & fragility. Change-Id: Ib0147e2aa2b710dfd627df7f535a685301214a52