Hi Kohei, On Tuesday, 2013-07-23 13:47:08 -0400, Kohei Yoshida wrote:
Of course it doesn't matter where we actually stick the "defined label" in, having them as part of the database range probably is best because we usually can derive it from the top-row of the database range (don't know currently if Excel allows more than one row for those Table labels, they did a very awkward thing with their labels back then).Noted. Perhaps it was that awkward-ness that prompted them to drop this feature in 2007? I'm just guessing.
Might be one of the reasons (that awkward feature btw was called Stacked Column Labels, we never implemented that in its implications though). I guess another reason is the introduction of the XML based file format, they probably encountered similar problems we do. The automatic lookup depends on the actual current content of the document, one can quite easily generate a document using automatic label lookup that when saved and reloaded again the new lookup actually matches a different cell due to a nearer cell having the matching content. That was no problem in binary formats where formulas didn't have to be recompiled. Of course issues with editing such a formula were also present back then. Sad that MS introduced it and we had to follow :-/ Having had to implement the space operator for intersection in this specific case didn't make things better and already drove me nuts by itself ;-) Really, space operator, wtf?!? (yes Excel intersections always work that way) Remember how the whole story was advertised? Natural Language Formulas ... <rant off> Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key ID: 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A For key transition see http://erack.de/key-transition-2013-01-10.txt.asc Support the FSFE, care about Free Software! https://fsfe.org/support/?erack
Attachment:
pgpjjLpHpFDx5.pgp
Description: PGP signature