https://bugs.kde.org/show_bug.cgi?id=512020
--- Comment #5 from pallaswept <[email protected]> --- (In reply to Ben Guy-Williams from comment #3) > If I right click a folder, I expect to create a folder inside it (unless I > right click the background). The background is the view folder, if you right-click the background you *did* right-click a folder. > - This makes PERFECT sense because the context menu is explicitly tied to > the item you clicked. Because you selected it when you clicked. The CONTEXT of the context menu, is the SELECTION. That's where it gets that name. Try selecting one item and then holding ctrl while you right-click another item. Now you have added the second item to the selection and opened a context menu which would perform actions on both of them. > However, GLOBAL shortcuts apply to the current view, not a specific item. Oh yeh? try pressing 'del' or 'F2' or 'enter' or 'ctrl+x' ;) This isn't a GLOBAL shortcut anyway. It only works within Dolphin, it's LOCAL. But whatever, semantics. The actions which the user invokes should be performed using the context the user provided. It's "Take THIS, and do THAT to it". > If they acted on the selected folder, it would feel wrong Some disagree, rightly so, because selecting the folder is the mechanism for the user to define the context to which the context menu will apply... and this is the challenge exactly. How can Dolphin be technically correct without making things confusing for users who find that the technically correct behaviour feels wrong, even though it's objectively right? > ... and what if two > folders are selected? what if nothing is selected, simply active? The standard ways to deal with ambiguous selections are to use the last selected item (oversimplifying: that's the one which is highlighted and also has a dashed box around it) or where that is not appropriate fall back to a default such as the view folder, or just disable that action under those contexts. Dolphin already does this. > I feel the SAME would apply to the 'global shortcut' Ctrl_Shift_N, which I > feel 'naturally' should create a folder in the current view (PWD). The trouble is that works in Windows Explorer all of the time because it doesn't have Dolphin's capabilities. In Dolphin, the working directory (CWD) is not necessarily the view folder, it might be the selected folder which might be N layers deeper than the view folder. This is a powerful feature for power users, but does bring usability challenges, like this bug. > The idea that these actions should all mix and match perfectly seems wrong > when psychology comes into play. Psychologically the issue is that people will refuse to admit a mistake was carried from a dissimilar application and learn a new way. This creates a challenge where the obvious and technically correct solution might generate a lot of complaints. Because it MUST be the solution that is a mistake, since the USER couldn't possibly be mistaken. > So perhaps a solution would be to offer two options if ambiguous This bug report is not regarding any kind of ambiguity though. In the context of this bug report, there's no ambiguity, the user's selection is clear. This bug is about Dolphin ignoring it. Dolphin already handles ambiguous selection (try selecting two folders and right-clicking (no menu item) or clicking the toolbar button (falls back to view folder)) and if there are problems with that, that probably should be a separate bug linked to this one. -- You are receiving this mail because: You are watching all bug changes.
