https://bugs.kde.org/show_bug.cgi?id=508196
--- Comment #53 from pallaswept <[email protected]> --- The same tired illogical arguments just keep repeating themselves... I guess now I have to repeat the same explanation here.... Yknow, on the off chance that anyone is actually interested in learning the error of their ways, and assuming people aren't just doing "I think it should work like this and therefore I am correct and will always be correct". This "all the others work like that, so this should work like that" argument, makes zero sense, is unproductive, and needs to stop. It's like complaining that your B-double truck is too slow and too big to fit in a parking lot at the shopping centre and it should be more like your hatchback, or that your racecar uses too much fuel and should be economic like your hatchback, or that your hatchback is too small to carry a forklift and too slow to win a race. The problem is not the vehicle, it is the false expectations of the driver. Dolphin is not all those file managers, it does things those file managers can't, it should not act like them, because it is not like them. > So regardless of “selected folder” the “Ctrl-Shift-N”, ”New folder” will be > created in the PWD. Understand: The "selected folder" *IS* the "PWD". You can't perform an operation in the "PWD" regardless of the "PWD". That makes no sense, obviously. PWD stands for "Print Working Directory", it is a command, not a location (actually it's not even a command, the command is "pwd"). You mean "CWD" which stands for "Current Working Directory". Using these terms interchangeably was done in the discuss thread for the purpose of continuity but should not leak out of it as it is incorrect. The 'CWD' is the directory you clicked on to select - not to be confused with the directory in the toolbar up top, which is NOT necessarily your current working directory, if you are working in some other directory, which is a thing you CAN do in dolphin and can NOT do in those other file managers you mentioned, and it is important that you begin to understand that, if you are going to provide meaningful input to this discussion. The path in the toolbar at the top does not define your working directory. It defines the root of the tree which is visible. The selected objects define your working objects, and if the selected object is a directory, that is your working directory. It's the same in Explorer. Try it with del or F2, instead of ctrl+shift+n. Try it comparing what happens if you click a file, or a folder, or the empty space in the background. Del = delete the thing I clicked. F2 = rename the thing I clicked. ctrl+shift+n = create a folder in the thing I just clicked. Note that Explorer is limited in its capability to handle subdirectories, so it limits your ability to do this. Note that Dolphin does not have Explorer's limited functionality when working with files and folders below the displayed location. This is the source of your confusion. On a related note: >There are exactly *three* people advocating for the change introduced here, >while literally *everyone else* is saying that this is not a good change and >that it breaks the UX. Why do it? Cui prodest? https://en.wikipedia.org/wiki/Argumentum_ad_populum Maybe those three people are objectively correct, and *everyone else is wrong*. That's a thing that can happen, I know that if you're one of the wrong ones, it might not feel fun to realise it, but, it is still a thing. It makes sense that in a population which is largely composed of new users fresh from Windows, those users are likely to be confused by a file manager that actually has what people requested for decades, was added to Explorer - a tree view, that allows them to view and select subdirectories of their location, to use as a working directory. But one thing that Windows and Explorer users will surely understand, is that using the mouse or keyboard to select an element of the user interface, anywhere in the OS, even outside of the file explorer, is the way for you to tell the computer than the actions you describe (like delete, copy, paste, create new folder, etc) are to be performed with that element as the target. For an example, start typing a reply. Select a word. copy it. Does it copy the thing you selected, or does it copy the entire post? So, when you say that dolphin doesn't act like "everything else", it actually does, if it creates the folder in the place where you selected. Every GUI works that way, and always has. Windows do break that rule for Explorer though, because it doesn't have the tree view. Dolphin does have the tree view, so it makes no sense for Dolphin to act like Explorer. You're just clicking on the wrong thing and then confused by the computer doing what you told it to do, because you didn't realise that you told the computer to do that, because in the app you're accustomed to, an app with less functionality, you cannot tell it to do that, and when you clicked in the wrong place, it would ignore you. Now that you're using a better app which can do that and doesn't ignore you, but does what you told it, it's throwing you for a loop. That's a real problem, nobody is denying that. Everyone wants dolphin to be intuitive. But to make it intuitive to users of an inferior tool, is not something best achieved by simply making Dolphin an inferior tool, too. -- You are receiving this mail because: You are watching all bug changes.
