[squeak-dev] bad UI bug introduced with recent list highlightiong changes.

Ken G. Brown kbrown at mac.com
Fri Apr 3 19:04:58 UTC 2015


Hmmm, when I tried, it happens as you say except C would stay selected afterwards. And It could be C+D+... initially selected. 
I'm on OS X 10.10.2 

Ken,
from my iPhone

> On Apr 3, 2015, at 12:00, tim Rowledge <tim at rowledge.org> wrote:
> 
> 
>> On 03-04-2015, at 10:41 AM, Ken G. Brown <kbrown at mac.com> wrote:
>> 
>> I think what Mail is doing is honoring any previous selection and treating a cntl-click menu selection as a separate operation, then puts you back to the state you were in before you initiated the action.
>> You get to operate either on the single message under the pointer at the time you cntl-click if it isn’t the current selection, or else the current selection if the pointer is over any part of the current selection, which may be more than one message.
>> 
>> To me this seems a bit better than losing the current selection when doing the cntl-click menu operation.
> 
> I’d agree with that last part if it were what appears to actually happen. But on my iMac it just isn’t the sequence.
> 
> A
> B
> C-selected
> D
> 
> right-click over A and the outline box appears around A, the menu appears. Make any choice - even no-choice - and A becomes the selected item and C is deselected.
> 
> One of the problem with discussing these things is that they often seem quite different in different contexts and what looks a great idea in one situation is a disaster in another. I one doesn’t use the case where it looks good you’re not going to be much in favour of the idea.
> 
> Where I *can* see this working well is in cases where there is a list that does not produce a selection affecting some content view. Imagine a list of items where you are able to choose from a few menu options relating to each one ( err, maybe delete/save/pass-to-supervisor) - then, right-click to open a menu specifically referring to the item under the pointer seems like it might make sense. 
> 
> Further out, I can imagine that we could make the concept work within the normal tools after some fairly major rejigging of how they work. Right now the whole usage pattern in the lists used in Browsers etc is that the menu acts on the list itself or *the selection previously set*. That, by the way, results in some bugs in places where the code doesn’t bother to check for a selection - try fileout in a browser message list where there is no selection.
> 
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Oxymorons: Good grief
> 
> 
> 


More information about the Squeak-dev mailing list