Version: git-latest (using Devel) OS: Linux At the moment one needs two clicks to open a chat window with a contact from the list. this is somehow inconsistent with what happens in the rest of the desktop. for example mine is configured to open things with one click... Reproducible: Didn't try Steps to Reproduce: open a chat with a contact Actual Results: two clicks needed Expected Results: one click or whatever is set in the desktop settings should be used. OS: Linux (x86_64) release 3.1.0-rc5-2-desktop Compiler: gcc
Do you think this should be changed because it's against convention or because you find the actual implementation annoying. The system setting entry says "double click opens files/folders" this is neither a file nor folder therefore we can do what we want without it being "wrong". Maxime has emailed KDE-usability.
I think the description in the system settings is wrong... is not only folders/files that open at one click. all the actions that I know of in kde workspace are 1 click. start menu, icons shortcuts, system try apps, navigation in plasmoids. the idea is just to be consistent and give the user to change the behaviour if he/she does not like it. following the systemsettings setting allows for integration. Alin
"is not only folders/files that open at one click. all the actions that I know of in kde workspace are 1 click." Yes but these actions are neither folder or files, ie. that setting does not apply to them (in other words, set it to double click and you'll still be able to open systray apps with single click). So in this case the system settings wouldn't apply at all. As for consistency - you must look at similar treeviews. Take Clementine/Amarok - single click expands the album (group) but only double click starts playing the song (starting the action). In this sense we're perfectly consistent.
One of the reasons for which I donot like the two apps you mention. and at the end of the day none of them is part of kde... on the other hand kde-telepathy wants to integrate itself in the kde workspace and it is important to offer a consistent experience at kde level...
Fair enough. However there appears to be some misunderstanding in KDE about the consistency. As Luis reported in 275413, "For usability and coherence with symilar lists in other kde apps, the groups [...] should expand on single click". So I look around KDE apps and found out they are a bit inconsistent themselves (note, that my setting is double click for folders/files). Konqueror's bookmarks sidepanel - groups are expanded by double click, pages opened by single click. System settings tree view - like Konq, groups by double, pages opened by single. KDE's Help - groups expand with single click, pages are shown with single as well. Akregator - click on group crashes it Kate's files sidebar - groups on double, files on single. However I feel we can't really compare these because these are *sidebars* with attached main view. Contact list is nothing like that, it's a standalone list with actions on it's items (so no simple click->display). Let's look further then: System monitor - groups on double click, no action on single click on items Well and that's all I really found in KDE that is not a sidebar-mainview thing. Excluding the media players mentioned on top. So I don't really know. If we want to be system consistent, we should change groups expanding to double click then (or system settings, not sure if all those above are obeying that). But then again, there's no similar app in KDE (except Kopete) like our contact list (stand-alone listview), so perhaps we could make it our way. Let's see what the usability team has to say about this.
Hi guys, at least Kopete used a single click to open a chat - and that was the prior KDE Chat program. And: system settings uses a single click in the normal view to access a config. and starting a chat is - at least to me - no different from opening a folder or a file. KMail2 uses a single click to show a Message or open a folder (double click on folder starts renaming) KDE's menu uses single click. Akgregator: click on group does nothing (use small arrow symbol), double click on group starts renaming. Single click on Feed opens the feed. I'm totally on Alin M Elena's side here. In fact I'm not a fan of double click opening in general... I've seen people double clicking in the Windows menu oder double clicking a link in firefox. A single click to open is more natural - see all current touch devices. The only reason I see for double click opening is marking - which was resolved quite good in KDE without double click. Kontact list of telepathy is currently a bit raw - but I'm really looking forward to see more. Good job. Greets Christian
Thanks for your input. As was mentioned before, our contact list is not any case you mentioned - a sidelist with main view. Of course it feels natural there because you are displaying a content, not starting an action like playing a song from amarok. In contact list, you starting an action, not displaying a content. -- Martin Klapetek | KDE Developer Sent from phone On Nov 9, 2011 3:30 AM, "christian tacke" <lordbluelight@gmx.de> wrote: > https://bugs.kde.org/show_bug.cgi?id=282361 > > > christian tacke <lordbluelight@gmx.de> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |lordbluelight@gmx.de > > > > > --- Comment #6 from christian tacke <lordbluelight gmx de> 2011-11-09 > 02:30:18 --- > Hi guys, > > at least Kopete used a single click to open a chat - and that was the > prior KDE > Chat program. > > And: system settings uses a single click in the normal view to access a > config. > and starting a chat is - at least to me - no different from opening a > folder or > a file. > KMail2 uses a single click to show a Message or open a folder (double > click on > folder starts renaming) > KDE's menu uses single click. > Akgregator: click on group does nothing (use small arrow symbol), double > click > on group starts renaming. Single click on Feed opens the feed. > > I'm totally on Alin M Elena's side here. > > In fact I'm not a fan of double click opening in general... I've seen > people > double clicking in the Windows menu oder double clicking a link in firefox. > A single click to open is more natural - see all current touch devices. The > only reason I see for double click opening is marking - which was resolved > quite good in KDE without double click. > > Kontact list of telepathy is currently a bit raw - but I'm really looking > forward to see more. Good job. > > Greets Christian > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. >
*** Bug 298471 has been marked as a duplicate of this bug. ***
At least, if you think that contact list should not use KDE folder options, i think contact list should always use single click... Don't see any good reason to use double click here...
Sorry, that's just your preference based solely on your personal feelings. And we can argue about this the whole day, because I think it should always be double click. Here's why: to prevent unwanted chats from easily opening. Consider touchpads (and maybe even people with harder hands movement) the chats could be popping up constantly even if they didn't wanted to, one bad touch and you have to navigate to close it again. So here goes one good reason for you why use double click.
I tried single click for a while (it's a one line patch). I accidentally opened a chat so many times that I had to revert. Note that when in full view and you click on the "start text chat" icon it opens on a single click, because it's really clear that's what you're doing. Same for starting a chat from the context menu. So we are following KDE conventions. Double clicking on a contact is just an added shortcut to opening a text chat, you don't have to double click and it's not the only reason you'd click on someone. Advice from KDE usability was to "follow what works", from my experience single click doesn't.
*** Bug 303699 has been marked as a duplicate of this bug. ***