Bug 66440

Summary: unexpected behaviour in file open dialog when selecting multiple files
Product: [Unmaintained] kfile Reporter: raspl
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description raspl 2003-10-23 07:44:28 UTC
Version:            (using KDE KDE 3.1.2)
Installed from:    SuSE RPMs

This bug relates to the common file-open dialog. As a sample, I'm using the one that appears in the control center, when loading multiple background images.
Open Control Center, go to desktop background->background picture (or something like that, I have the GErman version...) and hit the button 'setup for multiple pictures'. There, hit the 'add' button to get the file open dialog. Now navigate to a directory with lots of files - enough so that you have multiple columns. Files displayed will look like this:

 a_file   f_file   k_file
 b_file   g_file   ...
 c_file   h_file
 d_file   i_file
 e_file   j_file

now click on 'a_file', hold down shift, and click on 'h_file'. What is selected will be (selected files marked with a '*')

*a_file  *f_file k_file
*b_file  *g_file ...
*c_file  *h_file
 d_file   i_file
 e_file   j_file

But that is quite contradicting to how files are displayed! Holding down shift while selecting multiple files means 'select everything up to here'. Since files are sorted in columns, what should be selected should be rather all files up to 'h_file', which would be:

*a_file  *f_file k_file
*b_file  *g_file ...
*c_file  *h_file
*d_file   i_file
*e_file   j_file
Comment 1 Thiago Macieira 2003-10-24 01:51:13 UTC
That's consistent with how Konqueror operates. I don't see a problem here, so this has to be an usability bug.
Comment 2 Christoph Feck 2009-08-27 02:34:46 UTC
Moving from "kio/kfile" component to "kfile" product, helps sorting out duplicates.
Comment 3 Christoph Feck 2009-08-27 03:27:16 UTC

*** This bug has been marked as a duplicate of bug 119936 ***