Re: [orca-list] Update on (work-in-progress) presentation of selection changes in Calc

[Joanmarie Diggs <jdiggs igalia com>]

Hi Peter.

Thanks for your feedback. More inline.

On 07/11/2018 11:02 AM, Peter Vágner wrote:

[...]

> * Now keep holding down the shift key and press left arrow key. Orca
> says D1 through D2 unselected and C1 through C2 remains selected.

Right. Because Orca is announcing what changed since the last
announcement. Before you pressed Shift + Left Arrow, C1, C2, D1, and D2
were selected. After you pressed Shift + Left Arrow, D1 and D2 became
unselected. Nothing changed regarding the selection of C1 and C2.
Therefore Orca didn't say anything about C1 and C2.

> * Still keep the shift key held down and press left arrow key again.
> Orca will report B1 through B2 selected however infact b1 through C2 are
> selected at this point.

As a result of your pressing Shift + Left Arrow again, B1 and B2 got
added to the selection. C1 and C2 were selected before, and remained
selected after. Since nothing changed with respect to the selection of
C1 and C2, Orca didn't say anything about them.

The reason I went with this approach was for the following reasons:

1. Be consistent with what Orca does with text selection (i.e. when you
   select a new line of text, Orca doesn't read all the text; just what
   was newly selected. Ditto with unselection.)

2. Minimize chattiness and be consistent within single cell selection.
   If, say, A1 through A30 are already selected, and you press Shift +
   Down Arrow, you want to know immediately that A31 was selected.
   Having to wait for the announcement about the selected range starting
   with A1 is a waste of time (right?). I think this is also the case
   if you selected an entire row or an entire column and extended (or
   reduced) that selection by a row/column. So if in those cases, you
   just want to know what changed, why should Orca behave differently
   in your scenario?

Granted, I realize that this requires one to do a little more work in
one's head. I plan to address this through adding support for selected
cells in the whereAmI command, along with in the selected text command.
I hope to get to adding that soon.

Long way of saying.... I think the current behavior is a feature, not a
bug. :) Or at least, it's something I did on purpose. That said, if you
think it should be done differently, please describe the exact behavior
you expect, and let's see what the user community thinks.

Granted you did this below here:

> Also perhaps more of us would like to comment on this however I would
> prefer if orca will only report what is selected and not saying what has
> became unselected as with complex tables where a lot of arrow keys
> navigation is desired can quickly make me lost the chain of selections.

But I fear that the length of your message may result in this getting
lost. Therefore my suggestion, FWIW, is would be to start a new thread
in which you have one very short set of steps to reproduce with expected
results and actual results. Look at how Alex has reported recent issues.
I don't know about others on this list, but I personally find that style
really easy to digest.

Thanks!
--joanie