Re: [Evolution] Ambiguity between "highlighted" and "selected"

[Patrick O'Callaghan <poc usb ve>]

On Tue, 2016-01-12 at 14:20 +0100, Milan Crha wrote:
> On Tue, 2016-01-12 at 12:49 +0000, Patrick O'Callaghan wrote:
> > On switching to a message folder, the previously selected message
> > in
> > that folder is highlighted, however the message is not in fact
> > selected until the user clicks on it, so that hitting an arrow key
> > will jump to the next folder in lexical order, not to the next
> > message.
>
>       Hi,
> I suppose you selected the folder by mouse. As such, the folder tree
> on
> the left is focused, thus it gets the keyboard input...
>
> > However hitting Reply *will* bring up the composer on the
> > highlighted
> > message.
>
> ... unless the keystroke is defined as a short cut for some action,
> then the action is executed instead the keystroke being used by the
> focused widget.

Makes sense. I never select folders using the keyboard, always with the
mouse. However even if I select the folder with the keyboard, the rest
of the behaviour is the same, i.e. the message is not selected until I
click on it. I'm struggling to understand how this is supposed to work
if it's not as I described.

> > The situation changes once the user clicks on the message because
> > now
> > it is really and truly selected, but there is no visual change to
> > indicate this.
>
> That might be due to the GtkTreeView, which, intentionally, doesn't
> change background of the selected item in it to some "grey" from
> "blue"
> when the widget loses focus, which for example the message list does
> (the actual colors depend on the current theme). There is a bug
> report
> against gtk+ and GtkTreeView for this, resolved as that's on purpose.

Does resolved mean "this is on purpose and so won't change", or "it has
been fixed and the behaviour will change"?

poc