Re: PyUNO usability improvements

On 16/06/2015 21:45, Eike Rathke wrote:

> Is there a specific reason for this? Why not keep the order the API
> uses? My concern is, that if these get mixed the user will get
> confused..

Doing it the other way round would give a different obvious violation
of the principle of least confusion. Taking one of my original examples,

> tbl.Data = ((y for y in range(10*x,10*x + 10)) for x in range(10))

> tbl.Data
((0.0, 1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0),
 (10.0, 11.0, 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0, 19.0),
 (20.0, 21.0, 22.0, 23.0, 24.0, 25.0, 26.0, 27.0, 28.0, 29.0),
 (30.0, 31.0, 32.0, 33.0, 34.0, 35.0, 36.0, 37.0, 38.0, 39.0),
 (40.0, 41.0, 42.0, 43.0, 44.0, 45.0, 46.0, 47.0, 48.0, 49.0),
 (50.0, 51.0, 52.0, 53.0, 54.0, 55.0, 56.0, 57.0, 58.0, 59.0),
 (60.0, 61.0, 62.0, 63.0, 64.0, 65.0, 66.0, 67.0, 68.0, 69.0),
 (70.0, 71.0, 72.0, 73.0, 74.0, 75.0, 76.0, 77.0, 78.0, 79.0),
 (80.0, 81.0, 82.0, 83.0, 84.0, 85.0, 86.0, 87.0, 88.0, 89.0),
 (90.0, 91.0, 92.0, 93.0, 94.0, 95.0, 96.0, 97.0, 98.0, 99.0))

> tbl.Data[9][0]
90.0

> tbl[9,0].Value
90.0


If the XCellRange specialisation used c,r order, the last statement
would give 9, not 90

(The .Data comes from the XChartDataArray interface; there is also e.g.
.DataArray from XCellRangeData)

Regards
Matthew Francis