| Summary: | Is making kickoff lists not wrap an option? | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Albert Astals Cid <aacid> |
| Component: | Application Launcher (Kickoff) widget | Assignee: | Sebastian Kügler <sebas> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | CC: | aleixpol, jamboarder, kde, kde, mklapetek, notmart |
| Priority: | NOR | Flags: | aleixpol:
Usability+
kde: VisualDesign+ |
| Version First Reported In: | 5.1.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Albert Astals Cid
2014-11-16 00:44:09 UTC
Makes sense to me, I can see myself doing that in fact. even tough now wrapping makes it consistent with QMenu I don't think anyone would expect KickOff to work like a QMenu... My own thought is that wrapping lists obscures the consistency of the spatial model the user employs to determine location in a list by softening/masking the reference point provided by a hard beginning and end. As the bug report demonstrates, it also deprives the interaction of a sort of keyboard Fitt's Law benefit when trying to get to the beginning or end of a list. That doesn't mean I think wrapping should never be used, but that I think there are differences that have measurable interaction impacts. For this reason I tend to agree with the bug report. I'll go ahead and confirm, for now. Alt+F1, Arrow left once, arrow up once. That's quicker, even. It's not about quicker, it's about expectations, actually it's kind of weird i'm being asked for reasons to bring the old behaviour back. What are the reasons for changing the behaviour? Or is it just because QML makes it easy? Kai, this is as cryptic as it gets. Let's not think in those terms. I think that what Andrew said makes lots of sense. Then why is every menu in every operating system wrapping if it's such a bad idea? I do agree that the kickoff tabs should not. That's a good question. In fact it could be interesting if somebody could look into the famous usability study that ended up in the current implementation. ping? Any way we can get this moving forward and decide it's either a bug or a feature? I would like to point out that Kicker does wrap. I think it should go to either both or none (ie. they should stay consistent). Personally I think on the contrary that this should wrap. > it also deprives the interaction of a sort of keyboard Fitt's Law benefit when trying to get to the beginning or end of a list. But at the same time this gives the user a quick way to jump to the beginning or end of the list, saving you from many up arrow key strokes when you're at the bottom. As Kai pointed out, this could make things faster for power users (but even for ordinary ones). > there are differences that have measurable interaction impacts How would such differences be measured here (genuine question)? -- If the only actual reason for this would be to get quickly to shutdown, that's imo not a valid reason to change it. I guess at this point everyone is used at this thing wrapping, so let's just say you guys decided my request is a wontfix. |