TilePattern::global_at returns wrong offset

[devreal]

Can someone please shed some light on the following issue? I have a 2D NArray with TilePattern and use global_at to determine the global offsets of elements in the tiles. Consider the following example (numbers are unit IDs):

0 0 | 1 1 | 0 0 | 1 1
0 0 | 1 1 | 0 0 | 1 1
2 2 | 3 3 | 2 2 | 3 3
2 2 | 3 3 | 2 2 | 3 3 

If I try to get the global offsets of the first and last element of the block {0, 0}, I do

// first element in block {0, 0}
pattern.global_at({0, 0}); // returns 0, as expected
// last element in block {0, 0}
pattern.global_at({1, 1}); // returns 3, expected?

The second call to global_at returns 3, which is the offset inside the first block. The documentation of global_at states that it provides Global coordinates to global position in the pattern's iteration order. It is my understanding that the global iteration order is linear through the row and column, unlike the local iteration order. Thus, the second call to global_at should return 9.

Is my understanding of the term global iteration order incorrect or is TilePattern::global_at broken?

[rkowalewski]

Cannot help you really here because I still do not understand the pattern code. AFAIK you are right with your assumptions.