SingleReference flag 64 in token data

English
,
#1

If a cell contains a formula its .Tokens property is a non-empty array (sequence).
If the formula contains a reference, the respective token has .OpCode 0 and .Data which is in the simple case a structure of type com.sun.star.sheet.SingleReference. This structure holds a property .Flags telling mainly which parts of the reference should be treated as relative, if the tokens are moved(copied) to a different cell. The flags are additive and should be explained here.
I don’t understand the flag 64 which is named SHEET_3D and for which the more information doesn’t tell anything reasonable.

My experiments seem to show that this flag must be set if the resulting formula shall have an explicit sheet part at all.

Please explain this to me.

#2

3D range is a range where sheets are different: e.g., Sheet1.A1:Sheet2.B2.

#3

Thanks.

This is what is called a cuboid in the odf papers, and I also assumed a meaning in the sense of your example.
However, my observations seem to clearly show that without the flag 64 the tokens never print a formula with a sheet part.

#4

To see more clearly what I mean run the Sub contained in the attached example.
disask125516_demo.ods (12.7 KB)

#5

Flag 64 simply translates to a reference including the sheet name when the formula is parsed. It has nothing to do with 3D-references like Sheet1.A1:Sheet4:B5.

#6

Yes. That’s what I also found. Remains the question “Why the confusing name SHEET_3D?” … And the misleading description in the API reference.
I addition there were some strange observations when I moved tokens sequences to differen sheets.

#7

Because a reference with a sheet name refers to a cell on another sheet, unless the referring cell is on the referenced sheet itself. In user documentation (for Excel at least) 3D reference refers to things like Sheet1.A1:Sheet4:B5.

#8

This isn’t new, and my example shows that the effects are also as I described them if the document has only one sheet - and if the reference goes to a single cell. Nothing to do with Excel.
And once more: The confusing fact is that an attribute with the mentioned name isn’t in any way realated to “3D” ranges (cuboids).
No need to refer to Excel documentation. See this page.

#9

Oh my!
OpenDocument spec V1.3 part 4, subchapter 4.8 atually states in "clear words":
A cell cuboid consists of cell positions in the same cell rectangles of one or more contiguous sheets.
Why "cell positions" instead of "cells"?
Translation for flag 64: This reference is to be treated as a 1 x 1 x 1 cuboid.
No it doesn’t fit actrually. A cuboid should be described by a ComplexReference.
Regard that =A1 and =A1:A1 are treated differently.

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.