broken-e / DragDropConfirm

A simple shell extension for Windows to stop accidental drag and drop moves of folders.
Other
90 stars 25 forks source link

Mapped network drives #2

Closed mebert02 closed 6 years ago

mebert02 commented 9 years ago

The application works perfectly on local drives. As soon as I try to move or copy a file on a mapped network drive, I don't receive the prompt. I've tried it on Windows 7 as well as 8.1 with the same results.

broken-e commented 9 years ago

Hi @mebert02, that's strange as mapped drives work for me. Although my best guess is that windows is using a 32-bit shell behind the scenes when you are using the mapped drives (e.g. if you are in a "Save as..." dialog) and the installer was not installing the 32-bit dll. I've released a new version (and renamed the program to DragDropConfirm) and it will install the 32-bit dll as well as the 64-bit dll. So if what I suspect is true, this will help you. Please try that version, but be sure to uninstall the previous version first. Let me know if that works for you.

dgd2 commented 7 years ago

I am experiencing this (or a similar) issue on Windows 7. Dragging from local to local, or network to network works fine. If I try either network to local, or local to network, i don't get the "hold up there" prompt.

bduffek commented 7 years ago

In response to dgd2, are you moving or copying? It doesn't check for copying and the default operation will show a (+) as you drag. if you hold shift to move to another drive it should fire still.

Edit: As a side note holding shift while dragging forces a move, ctrl forces copy, and alt forces shortcut creation. These keyboard shortcuts do in fact trigger the text required for this extension. As per the reference below I did my try at adding functionality for catching copy.

bduffek commented 6 years ago

This was almost certainly due to copy operations, which are now supported to be checked. https://github.com/broken-e/DragDropConfirm/commit/bb608ed3ba7e224e5ca5a6d0b5f9cc199c10374b If anyone has issues with this please open a new issue.