Yep that's the exact same "bug" I'm facing. Audacity is definitely not physically moving the file on the disk, nor is it editing/modifying it. Plus, when refreshing the Mp3tag file list interface the fiile shows back up.
This is only a recent bug. I'm not sure whether it's a Windows update, Audacity update or Mp3tag update triggering it. Is there any way we can disable this from happening? Plus, it raises the question, what is the "Keep moved files in file list" option if not for resolving this?
It is not MP3tag that determines what happens to the files but the accepting application.
So please turn to the Audacity developers and tell them that this is not the way you like it.
The option that you quote is an option to set whether you still want to see files in MP3tag that have been moved by MP3tag to a different folder than the current working directory.
Thanks! It's actually not Audacity inducing this behaviour, but the latest Windows 10 update. I've verified by using the latest Audacity versions on two machines, one with all Windows Updates installed and one without.
The Windows machine with all updates installed will make the file vanish from Mp3tag, but the machine without updates will not. Furthermore, I have just updated the eldest machine to the latest Windows Updates and now the same bad behaviour is observed on both.
I'm not sure whether it is Explorer or Audacity's changed behaviour but I will take this up with the Audacity team like you mentioned.
PS, the weirdest thing though. One machine is still removing the file when I drag it out of Mp3tag to Explorer, but one is not. (:
I've reviewed the code in question again and it still holds. Audacity returns DROPEFFECT_MOVE at drag and drop without any modifier keys pressed and DROPEFFECT_COPY when Ctrl is pressed.
When the target app of the drag and drop reports that files are moved, I have no other chance than removing the files from the file list. I have no indication of where the files are moved to and would end up with orphaned files on actual moves.
One option to circumvent these problems would be to disallow move operations via drag and drop from Mp3tag all together. However, this would probably and most likely disappoint people who are using the feature as intended.