Summary: | Files are unselected on drag&drop even if cancel is pressed later | ||
---|---|---|---|
Product: | [Applications] krusader | Reporter: | Toni Asensi Esteve <toni.asensi> |
Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | krusader-bugs-null, nikita+kde |
Priority: | NOR | Keywords: | reproducible, triaged |
Version: | 2.7.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Toni Asensi Esteve
2017-10-16 22:29:54 UTC
Toni, can you share the link to krusader-users ML discussion? Since "Unselect files before copy/move" is a feasible workaround, I'm moving this to wishlist for now. I haven't got "but it would also have that effect nowadays: unwanted unselected files after a drag&drop" - why is this unwanted? > Toni, can you share the link to krusader-users ML discussion? Yes, a link is https://groups.google.com/forum/#!msg/krusader-users/EAfQ8xyK938/U0npK5Q5BAAJ > Since "Unselect files before copy/move" is a feasible workaround, I'm moving this to wishlist for now. I wouldn't say so, we have also to take into account that new Krusader users (and Krusader users that do not know about this new subject) have to, manually, unselect files after every copy/move operation (as they are not aware of the "Unselect files before copy/move" checkbox) and they are used to work as Krusader did (and as Midnight Commander, Total Commander, etc. do). This is annoying for them :-( > I haven't got "but it would also have that effect nowadays: unwanted unselected files after a drag&drop" - why is this unwanted? If nowadays the user goes to Settings > Configure Krusader... > Panel and checks "Unselect files before copy/move" then file deselections seems to work like in other programs (Total Commander, Midnight Commander) although... if he uses drag&drop, and cancels the operation, then the files are unselected (normally the user doesn't want that, because no copy/move operation was done). Greetings! I read the thread, tried myself and agree that current behavior is buggy with "Unselect files before copy/move" turned on (switching importance back). I'm not sure if "Unselect files after copy/move" will solve the usability problem completely, because these file ops are outsourced to background and user may want to move on before the actual process is done, especially for long copy ops. I think we need to at least solve drag&drop problem described in the thread. > I think we need to at least solve drag&drop problem described in the thread.
Yes!
With "Unselect files before copy/move = Yes" if user uses drag&drop, and cancels the operation, then the files are unselected (normally the user doesn't want that, because no copy/move operation was done). |