[Sugar-devel] [DESIGN] palette timeouts (was Re: #1169 NORM: Drop down menus give no indication of their existence, also are too slow to load.)

[Simon Schampijer]

Hi Gary,

On 09/08/2010 05:51 PM, Gary Martin wrote:
> Hi Tomeu,
>
> On 8 Sep 2010, at 10:30, Tomeu Vizoso<tomeu at sugarlabs.org>  wrote:
>
>> Hi,
>>
>> looks like Seeta is interested in doing something about this.
>>
>> Do we have any kind of agreement on what changes should be done?
>
>  From that ticket there seems to be agreement on making a left click immediately raise a palette where there is no other primary action. Should I start filing enhancement request tickets for each case I can find? Example: For the owners buddy icon, in all cases, a single left click should open the 'Shutdown, Logout, My settings, Register' palette.

+1 Fwiw, we did so for the journal sort toolbar button [1]. Yes, filing 
tickets for each case so that we gain an overall same feeling would be 
fantastic!

[1] 
http://git.sugarlabs.org/projects/sugar/repos/mainline/blobs/master/src/jarabe/journal/journaltoolbox.py#line248

> Regarding the secondary palette timing, a delay is there for several sane reasons:
>
>    - hiding advanced and infrequently used features one level down to reduce UI complexity**
>    - delaying the palettes from obscuring other parts of the UI a user may be trying to get to

Yes, I am mostly worried about false triggers, too.

> ** we must be open to sorting out cases where we have the priority wrong, the home view activity resume vs. start new is a clear example that needs resolving (e.g. resume and start new need to be given equal UI priority).

Right, we know already how to solve that particular issue (resume vs 
start new).

> How long the delay should be is not so obvious.
>
> Also be aware of future touch input, where a single tap would be equivalent of a left click, and a tap with hold would raise the palette, FWIW there is no good right click in a touch world —some folks are using two and three fingered touches but these are pretty obscure and unnatural to use, especially for small button sized targets; might be OK for something like raising/lowering the frame when allowed anywhere on the touch surface.

FWIW, my learners really nearly never use right click. Even so I told 
them several times. They wait for the palette to appear. Maybe the 
equivalents with touch point inputs will work better - will be 
interesting to see.

Regards,
    Simon

PS: Thanks Tomeu for bringing this to the surface!