Since Dolphin 2.0, directories are not expanded when double-clicked in the folder panel. This makes navigating by double-clicking impossible to do in the folder panel. For example, assume I have a directory named Documents under my home directory, and another directory named Music under my Documents directory. Currently, if I double-click on Documents in the folder panel, the contents of the directory will appear in the browser pane, but the folder does not expand in the folder panel. I need to either click the twisty next to Documents in order to expand it and see Music, or double click on Music in the browser pane in order to expand Documents in the folder panel. What would be expected (and the previous behavior) is that, when I double-click on Documents in the folder panel, the contents of Documents is shown in the browser pane AND the Documents directory in the folder pane is expanded so I can see Music as well as any other subdirectories listed under it for faster/easier browsing.
I can confirm this behaviour is still present in KDE SC 4.9RC1.
This is still an issue in 4.9.0 as well. Has anyone had a chance to look at it? This is a pretty clear regression from the 2.0/4.8 release, and while I know it's not a critical bug, it does hamper usability. I was hoping this would've been addressed by 4.9.0.
Resetting assignee to default as per bug #305719
Review-Request: https://git.reviewboard.kde.org/r/106497/
Git commit 3cb15ca7a116bccdb6f60611d60f2839cf1f924b by Emmanuel Pescosta. Committed on 20/09/2012 at 17:56. Pushed by emmanuelp into branch 'KDE/4.9'. Restore old behavior: Navigating by double-clicking in folder panel (Double-Click - show folder content and expand folder) REVIEW: 106497 FIXED-IN: 4.9.2 M +19 -0 dolphin/src/kitemviews/kitemlistcontroller.cpp M +10 -0 dolphin/src/kitemviews/kitemlistcontroller.h M +1 -0 dolphin/src/panels/folders/folderspanel.cpp http://commits.kde.org/kde-baseapps/3cb15ca7a116bccdb6f60611d60f2839cf1f924b
Yes! Thanks, emmanuel099. I actually tried testing your patch last night so I could give you some feedback, but couldn't get it to apply against stock 4.9.1. I'm guessing some other changes had already been made to these components there were causing some conflicts. Regardless, though, I'm thrilled to see this will be fixed in 4.9.2. Great news.