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

Tobias Pape Das.Linux at gmx.de
Fri Apr 3 15:24:31 UTC 2015


On 03.04.2015, at 17:12, Eliot Miranda <eliot.miranda at gmail.com> wrote:

> Hi Tobias,
> 
> 
> On Apr 3, 2015, at 4:20 AM, Tobias Pape <Das.Linux at gmx.de> wrote:
> 
>> Hi Eliot
>> 
>> On 03.04.2015, at 01:36, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>> 
>>> On Thu, Apr 2, 2015 at 3:56 PM, Tobias Pape <Das.Linux at gmx.de> wrote:
>>> 
>>> On 03.04.2015, at 00:43, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>>> 
>>>> Hi All,
>>>> 
>>>>   since the hover highlight changes, where the list element under the mouse that would be selected if one clicks is highlighted in light blue appears to have caused a bad bug.  If one does a right-button clock to bring up a menu the system can end up selecting the item under the mouse before putting up the menu.  This is *wrong*.  The mouse click to bring up a menu should /not/ change the selection.
>>> 
>>> The rightclick must change the selection, at
>>> least _temporarily_ to highlight for what item the menu is constructed.
>>> 
>>> The menu is constructed for *the selected item*, not for the item under the mouse click.   Try this.  Run the debugger on a large class.  In the instance variables list type some chaacter to select inst vars beginning with that name, then select one, then try and issue a right-click to explore the selected inst var.  Poof, the filtered inst vars disappear, to be replaced by all inst vars, and then explore applies to some completely unintended selection that isn't even in the list one thought one was selecting from.
>> 
>> I thought about what you described there once again, and just to report my experience,
>> this scenario is the exact time I use the #menuButtonInToolPane preference. When I have
>> an out-of-sight element I want a menu for (or no selection at all), I find it really convenient
>> to have this little button above the scroll bar. Also, it is explicit: when I click on
>> this menu thing, I don't point at something else but the "I want a menu now" button.
> 
> That makes sense and one could soon learn to use that effectively.  But if still means a mouse move before issuing the menu click, and I suspect I'll still find that tiring.
> 
> Sorry for shouting when I raised this thread.  
> 

Emotions are fine sometimes :)
Best
	-Tobias

>> 
>> HTH
>> Best
>>   -Tobias
>> 
>>> Please, please, please fix this quickly.  The system is /very/ difficult for me to use right now.
>>> 
>>> 
>>> Else, we need a kind-of “second selection”
>>> 
>>> No we don't.  Issuing a red button/left button click changes selections.  Issuing *other* mouse button clicks *should not*.  Right?  It's simple.  Right?
>>> 
>>> Best
>>>       -Tobias




More information about the Squeak-dev mailing list