Version: (using KDE 4.1.3) Installed from: Ubuntu Packages I want to move images between directories. So I select some images and press "move to" so the window for moving opens. It opens with a default directory, for example /media/goodbye If I click on the address bar and write with the keyboard another address for example /media/hello and click on the move button, gwenview WILL move the photos in /media/goodbye NOT in /media/hello !! To avoid this, after you wrote the address, you must press enter on the keyboard to make gwenview read the directory. This is so useless imho. Some hours ago I forgot almost everywhere lots of photos because I didn't know that you must press enter before clicking on the move button
This window is KFileDialog, a part of kdelibs, so I am reassigning the bug.
This is pretty standard behavior everywhere for the path field: you need to type return or enter, or click the checkmark button. If this wasn't a requirement, how would it know that you were done typing and had actually successfully navigated to the path you entered? Furthermore, entering paths in this UI is pretty much an expert feature (normal users don't easily grasp file paths), and I would expect experts to be able to hit return or click the checkmark--and notice that something was amiss if the view didn't visibly change after they failed to do so.
(In reply to Nate Graham from comment #2) > This is pretty standard behavior everywhere for the path field: you need to > type return or enter, or click the checkmark button. If this wasn't a > requirement, how would it know that you were done typing and had actually > successfully navigated to the path you entered? > > Furthermore, entering paths in this UI is pretty much an expert feature > (normal users don't easily grasp file paths), and I would expect experts to > be able to hit return or click the checkmark--and notice that something was > amiss if the view didn't visibly change after they failed to do so. I was curious and I have tried to reproduce the proccedure, and luckly this 9 years old KDE 4.1.3 bugreport does no longer apply on Plasma 5 :-)
*** Bug 82832 has been marked as a duplicate of this bug. ***