When using dolphin in detail mode with expandable folders, if I expand a folder by clicking on the '+' it highlights that folder name and all other folder names in the list as 'selected' and any operation, such as 'copy' acts on all highlighted items. Unwanted items can be deselected by clicking on the desired item name, but if I forget to do so I can make a big mess when applying mass operations - like 'delete'. Reproducible: Always Steps to Reproduce: 1.Open Dolphin in detail mode with expandable folders 2.Click on the '+' on one of the folders down the list to expand it 3. Actual Results: That folder name and every entry above it will be highlighted. Expected Results: It should have highlighted only the name of the folder I opened. I have also noticed this happening when I click on a .jpeg to open it in Gwenview. AFTER the picture loads in Gwenview, all items (folders and filenames) above it are highlighted. Running Kubuntu 14.04 LTS on an IBM Thinkcentre
Created attachment 93642 [details] Unwanted highlighting In this picture, I had only clicked on the gpodder folder to expand it. Every item above it was also highlighted.
Thanks for the bug report. This issue has been fixed some time ago - please upgrade to Dolphin 4.14 or later. *** This bug has been marked as a duplicate of bug 329377 ***
Thank you. I have been updating my system using the Kubuntu repositories and that gives be version 4:4.3 as the latest. It's probably because I'm running Kubuntu 14.04 LTS instead of a newer version. On 07/23/2015 12:17 PM, Frank Reininghaus wrote: > https://bugs.kde.org/show_bug.cgi?id=350347 > > Frank Reininghaus <frank78ac@googlemail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |DUPLICATE > Status|UNCONFIRMED |RESOLVED > CC| |frank78ac@googlemail.com > > --- Comment #2 from Frank Reininghaus <frank78ac@googlemail.com> --- > Thanks for the bug report. This issue has been fixed some time ago - please > upgrade to Dolphin 4.14 or later. > > *** This bug has been marked as a duplicate of bug 329377 *** >