Version: unspecified (using KDE 4.5.85)
When using dolphin's 'double-click' to open files/folders, multiple file selection drag & drop functionality for folder view widgets is broken. If you change dolphin to single-click, intended functionality is restored.
Reproducible: Didn't try
Steps to Reproduce:
1. Dolphin -> Settings menu -> Configure dolphin -> Navigation tab.
2. Select 'double-click to open files/folders'.
3. Group a few files/folders in widget and attempt to drag drop with cursor to another folder view/dolphin file manager.
The cursor selection of multiple items 'resets' hence unable to drag & drop.
Regression started with 4.5.80 and is still present in 4.5.85.
Can confirm on Arch [kde-unstable] 4.5.80 and 4.5.85.
Same here on my Arch with KDE 4.5.85, too.
Confirmed. When Dolphin is set to Double-click for navigation then it's impossible to select anything in Folderview. It's then impossible to drag stuff from Folderview.
trunk kdebase revision 1205142
Any chance we could expect this targeted for the 4.6 RC?
Still present in 4.5.90 (4.6-RC1)
*** Bug 261289 has been marked as a duplicate of this bug. ***
Still present in 4.5.95 and to be honest I can't imagine WHY?
unfortunately i can confirm rc2 is still bugged.
Does it work correctly when you configure "double click" globally in system settings? (Input Devices -> Mouse).
(In reply to comment #9)
> Does it work correctly when you configure "double click" globally in system
> settings? (Input Devices -> Mouse).
It would be a shame if this was not fixed for the 4.6 release... considering the folderview widget is displayed by default on every new install...
Any chance we could have some light shed on this by a dev?
Still broken on 4.6RC
Still broken in the release version of KDE 4.6
*** Bug 264505 has been marked as a duplicate of this bug. ***
*** Bug 264751 has been marked as a duplicate of this bug. ***
"Still present in 4.5.95 and to be honest I can't imagine WHY?"
that's an easy one to answer: because no one (including the people commenting on this report) contributed a patch to fix it.
our resources are limited such that we can't get to every bug and regression in such a finite amount of time. that double click isn't the default setting only lowered the odds (and making the "it's on every install by default" argument a moot point).
in any case, i'm taking a look at it now. it's just a bit discouraging to come to look at a bug report to start working on it and see these kinds of comments. :/
maybe at some point in the future my days will have 48 hours and i'll have 8 hands and 4 sets of eyes. until them, patience is appreciated.
Yay! \o/ Aaron <3 :-)
Ok, then implicitly the feedback is "why on earth is double-click NOT the default behavior?"
Just more KDE-being-KDE-for-KDE's-sake
@TR Reardon: "Just more KDE-being-KDE-for-KDE's-sake"
really? that's your first bit of input on this report, even after it's been fixed? what a pathetic, rotten attitude.
if nothing else, it has convinced me that i'm done working on software in my spare time for the weekend. feel free to take responsibility for the bugs that go unfixed as a result.
and to answer your question: it's because it is proven to have better usability for most people.
First up, thanks Aaron for your comments and coding contributions.
Please don't confuse my comments as being ungrateful - but I was perhaps impatient. My only niggling issue here is that this was confirmed for ~7 weeks with no official input/acknowledgment. If a dev is short on time or the regression is not as simple a fix as it should be then a short comment informing us of this could encourage others to take a look at the code and hopefully more patches will get submitted?
"If a dev is short on time or the regression is not as simple a fix as it should be then a short comment informing us of this could encourage others to take a look at the code and hopefully more patches will get submitted?"
i get somewhere between 50 and 100 bugs.kde.org emails _per day_, depending on the day, and these days i'm only subscribed to the ones related to plasma. i already spend, quite literally, as much time as i reasonably can doing bug triage. and i have other responsibilities as well, with people happy to be unhappy with me if those don't get done. ;)
we have a few people who help out with bug triage and they are absolute heroes. more would be wonderful.
but seriously, it's not like these bugs go unfixed (or uncommented on) because we don't care or aren't aware that it'd be nice to comment on each report at each release milestone. it's seriously an issue of manpower.
btw, Anne-Marie is a plasma developer and she did comment on this one.
"encourage others to take a look at the code and hopefully more patches will get submitted"
another bit of feedback on this idea: we do, pretty regularly, ask for patches and involvement. a lot of the time we get back snarky remarks about how we're just always asking for people to fix it themselves or "be quiet" (which is not what we are suggesting when we ask people to get involved and help fix things).
so there is no particularly great choice when it comes to dealing with bugs.kde.org, or more specifically, the people on the other end of bugs.kde.org: pretty much no matter what we do other than "fix it NOW" there's someone out there who'll be sure that i get my daily dose of 5-10 complaints by email. it's pretty unenjoyable to be on the receiving end of that year after year. no amount of "wow, we appreciate your work/efforts" really makes up for it, to be honest.
fortunately, we do get a reasonable number of fixes by asking for participation, though certainly it's a numbers game: ask 100 times and get 2-3 patches. and there are a good number of truly nice people around here as well. and as i get to know who they are, i tend to spend more time on issues they report, for what should be obvious reasons.
and in this particular case, one might have hoped that if there was 7 weeks of no fixes that someone who was affected by this and was hoping for a fix would have taken the initiative, maybe asked where to start looking. that's perhaps as realistic as having expected me to have fixed it sooner myself, though.
as an ex-dev of several open source projects i know what Aaron means, and how it may hurt to read some kind of complains while a simple "thank you" would be enough.
of course from user point of view, with such settings, it's normal to think "how the hell they didn't notice and spend time on this", but there are several way to say the same thing, keeping respect for free devs.
from my side i would like to thank Aaron for the fix, asking the svn revision link, so i can backport to 4.6.0 and fill a bug for this in gentoo bugzilla before it gets flooded.
jeah i would like to thank aaron too :) but you probably know that 99% of people absolutely love the work you do. Sadly there is no ban functionality for bugzilla, so we have to endure those trolls that only have one thing in mind, destroy the kde project by discouraging the developers. don't let them succeed!
40e65658 is the commit that fixed this in KDE/4.6 branch.
Patch applied to openSUSE KDE 4.6 packages.
Hi Will, can you give me a link to web git? or patch?
i can't find the commit id....me dumb :(
Patrizio, I believe http://quickgit.kde.org/index.php?p=kde-baseapps.git&a=summary is the repository, from there
git log --stat plasma/applets/folderview/
gives some commit messages that seem likely :-)
(all the other applets seem to be in another repository, so I guess that might be confusing)
yes but at the moment i don't have the git tool thus i cannot check from the web!
(In reply to comment #29)
> yes but at the moment i don't have the git tool thus i cannot check from the
Just got the fix across entropy in my Sabayon machine. Thanks for getting on it, devs. KDE rocks and I'd still use a buggy KDE over GDM (no disrespect to the Gnome folks). Your time is appreciated.