Bug 178871 - Selecting files with SHIFT works differently if triggered with the keyboard or using the mouse.
Summary: Selecting files with SHIFT works differently if triggered with the keyboard o...
Status: RESOLVED DUPLICATE of bug 163451
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-27 11:39 UTC by FiNeX
Modified: 2008-12-27 11:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description FiNeX 2008-12-27 11:39:16 UTC
Bug reproducible only on icon view:

Case A:

1) select one single file focusing it with the keyboard
2) press "SHIFT" key and keep it pressed
3) with the mouse click on another file OR, with the arrow keys, change the current file.
-> All files between the first and the last will be selected.

This is what an user expect and it is correct.

Case B:

1) select one single file using the mouse (not using the keyboard like case A)
2) press "SHIFT" key and keep it pressed
3) with the mouse click on another file OR, with the arrow keys, change the current file.
-> No file is selected and only the "focus" (dotted rectangle around the file name) is visible on the last file where whe have stop on third step.

Case B should behave like case A: when a file is selected with the mouse it have to be possible to select multiple files using SHIFT+click.
Comment 1 FiNeX 2008-12-27 11:41:44 UTC
Case C: 

1) Select the first file using CTRL+click
2) press "SHIFT" key and keep it pressed
3) with the mouse click on another file OR, with the arrow keys, change the
current file.
-> All files between the first and the last will be selected.

So the problem is only when the first file is selected with the "+" arrow or drawing a selection around the first.
Comment 2 FiNeX 2008-12-27 11:42:43 UTC

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