API for xIndexAccess of text selection

[jeanmi2403]

Hello,
What intrigues me is the structure of the selection list, and the fact that this was what caused the error in the `capitalise.py` example.
So, it is the behavior (and design logic) of `xIndexAccess` that I am struggling to understand.
Reminder:
No selection : one element at index 0 (empty)
One selected object : one element at index 0 (contains the selection)
N objects (N>1) : N+1 elements, the first (index 0) being empty.
This strange behavior (in my view) is visible in the short exercise that follows.

TestSelectionsPython-en.odt

Traverse the selected zones

(22.54 KiB) Downloaded 169 times

Can anyone explain this behavior?

[karolus]

No selection : one element at index 0 (empty)

There is no »no Selection« in writer, at least one selection exists (probably empty) at the position of the View-Cursor!

[jeanmi2403]

There is no »no Selection« in writer, at least one selection exists (probably empty) at the position of the View-Cursor!

Ok.
My question is : Why do two selections produce a 3-element array where the first element is empty?

[karolus]

There is no »no Selection« in writer, at least one selection exists (probably empty) at the position of the View-Cursor!

Ok.
My question is : Why do two selections produce a 3-element array where the first element is empty?

because your »two-selections-container« is in real a »three-selections-container« (including the »empty« …ViewCursor-object)

[jeanmi2403]

And doesn't a lonely selection have an empty counterpart?
It is hard to find any consistency.