[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: [KDE Usability] Treeview behavior
From:       Celeste Lyn Paul <celeste () kde ! org>
Date:       2011-09-30 23:39:50
Message-ID: CAAfNz7ZE7o+De4TkwhAz7dSORzAR-39+FkZ8paQQ-5H83TN=gQ () mail ! gmail ! com
[Download RAW message or body]

I tend to agree with David. Regardless of the click configuration, if
you interact with a normal tree widget, a single click will always
expand and collapse it. The mechanism you use -- whether it is the + -
widget, and icon, or simple a label -- should behave the same way.
Then, the action (in this case activating the chat by interacting with
the name) should follow whatever the system setting is: single or
double click.

You can't control if some users understand the interaction model they
have configured and others do not. You can only design for what you
can assume. We're going to assume the users are familiar and aware of
what they have configured.

Then again, once you have changed the interaction, you can always
observe how user's perceive the system and adjust when necessary as
well :)

~ Celeste

On Thu, Sep 29, 2011 at 7:19 PM, David Edmundson
<david@davidedmundson.co.uk> wrote:
> 2011/9/29 Maxime Corteel <mcorteel@gmail.com>:
>> Hello everyone,
>> I'm working with the kde-telepathy team and we have an embarassing usability
>> question.
>> Our contact list component uses a modified QTreeView where headers are
>> hand-painted and expansion arrows (the triangular thing on the left) can't
>> be used to expand categories. Because of that, you can just click or double
>> click on the whole header to expand the category (see [1]).
>> The question is : how do we handle double/single click system settings?
>> The best thing I can think of is :
>>  * When the system is set to single click:
>>    - A single click on a header expands/collapses the category
>>    - A single click on a contact opens a conversation
>>  * When the system is set to double click:
>>    - A double click on a header expands/collapses the category
>>    - A double click on a contact opens a conversation.
>> The problem is that some of us complain about single click starting a
>> conversation (because it would be too easy to start a conversation and you
>> can trigger it by accident)
>> So what does the usability team recommend?
>> Regards,
>> Maxime Corteel
>> [1] http://imageshack.us/f/90/telepathyclheaderandcon.png/
>> _______________________________________________
>> KDE-Telepathy mailing list
>> KDE-Telepathy@kde.org
>> https://mail.kde.org/mailman/listinfo/kde-telepathy
>>
>>
> Just to help give some backstory.
>
> Currently the KDE Tp contact list completely disregards all system
> settings with regards to single / double click.
>
> We have:
>  - open/collapsing group headers is always done by a single click
>  - start a conversation with a contact requires a double click
>
> We've had one bug report saying "we should follow the system settings".
>
> @Maxime
> I personally think group expansion in a tree view should always be on
> single click. If you change your system settings setting, all other
> apps still do this.
>
> The system setting configuration is "open files on single /double
> click". So nothing about treeview headers. Single click is consistent.
>
> However clicking a contact to start a chat is arguably like opening a
> file - and we should follow this setting.
> Or should it? I feel it would be far too easy to start many
> conversation windows by accident.
> _______________________________________________
> kde-usability mailing list
> kde-usability@kde.org
> https://mail.kde.org/mailman/listinfo/kde-usability
>



-- 
Celeste Lyn Paul
KDE Usability Project
KDE e.V. Board of Directors
www.kde.org
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic