When drag and dropping files between dolphin windows, there is a lag when pressing a modifier key to when it takes effect. For example, I can press and hold shift, but if I release the file before up to second after pressing shift, it won't actually take hold right away.
Thanks for the bug report, but I cannot reproduce the problem. If I release the Shift key and drop the item just a tiny fraction of a second after that, the Copy/Move/Link menu appears as it should.
I cannot reproduce it either
I just tested it some more, and when you click and drag a file from one window to another real quickly, it never drops, all without modifier keys. I believe that is related to what was happening to me before. That at least is completely reproducible for me.
(In reply to comment #3) > I just tested it some more, and when you click and drag a file from one > window to another real quickly, it never drops, all without modifier keys. That's probably because the Dolphin window where the item is dropped has not received the "focus in" event yet at the time of the drop. I'm afraid that there's not much that we can do about that.
When I first open up two folders that are on a samba share, and then I drag and drop them quickly while holding shift, it will act like I was holding control and try to copy them instead of moving them, so it seems like there is more going on than just focus issues?
(In reply to comment #5) > When I first open up two folders that are on a samba share, and then I drag > and drop them quickly while holding shift, it will act like I was holding > control and try to copy them instead of moving them Hm, I don't have any Samba shares to test with. Does that only happen with Samba shares? Do all other modifier keys work fine on Samba shares for you?
I have only noticed it with samba so far. I have only tested it with ctrl and shift.
Can you still reproduce the problem with Dolphin 4.11.2?
yes. It can also happen outside of samba, most noticible when the hard drive is busy.
This should be a duplicate of #352177 *** This bug has been marked as a duplicate of bug 352177 ***