Thanks for confirming the version used. But it doesn't really matter. It has been demonstrated already on several versions up to the very latest as of today v3.34-beta4 and the functionality has not changed.
It is unfortunate that there was some loss of files in this case. Hopefully all are recoverable from their original source.
The lesson here it to always have backups (yes plural!) of valuable data. And try features of any new software on a copy of a subset of files before moving into your live data for action.
Yeah but even with that I think there’s room for improvement on UX here
at first i tought a popup at first launch would be nice but that’s not enough and people doesn’t read.
Maybe the “delete” function shouldn’t be activate by default.
For me mp3tag was always about tagging mp3… and i’ve never realise it had also permissions to delete files. Altough I understand it can be helpful to have the function inside the software.
If I untick this setting I still get a (somewhat different) warning message in my Linux/Wine setup. I assume it's the Linux OS that issues this warning.
So at least in theory the behaviour could also differ between Windows versions (and possibly settings), but I haven't tested. Perhaps they do behave the same, or perhaps Mp3tag manages to suppress a potential Windows warning.
Sorry if this has little relevance at this stage - just saying that Windows 7/8/10/11 could differ in this regard. Mp3tag itself does give you its own warning by default settings.
By default
- you have to press the Ctrl key to call the more dangerous function that actually removes files from the file system - a simple Delete can be undone with F5.
- there is a message that warns you that you are going to remove files from the file system
- files move to the recycle bin (if this is supported by the file system
So it 2 modified settings of the default (of which one is also dangerous for all other potentially unintentially deleted files from other applications) plus an extra key stroke to really remove files.
IMHO more safeguards would reduce usability considerably.
E.g.: Deleting files from the file list (not from the file system) may be required to get playlists right.
Deleting files from the file system directly from within MP3tag is much more convenient than to
- detect a superfluous file,
- open the Explorer,
- navigate to the file's location,
- delete the file,
- refresh the file list in MP3tag.
You would also have to untick the setting for the recycle bin "Dialogue to confirm the deletion" to avoid all messages.
("Dialog zur Bestätigung des Löschvorgangs anzeigen")
Which would mean that even more safeguards were bypassed prior to the loss of the 30GB.
There is one more "dangerous" Mp3tag keyboard shortcut:
Ctrl + Shift + Del
From the documentation:
As the documentation says:
The file will be removed from your harddrive and not moved to the Recycle Bin.
The warn message appears according the individual File -> Option -> Messages settings.
I get that but it would just take 1 more setup in option to permanently be able to delete file.
I may be the only one reporting that UX problem but it doesn’t mean I’m alone out there
Again, I think very few people downloading the software realise it could potentially delete file
thank for the screen, I have to check that with my friend
Please note that you can set the Windows Recycle Bin settings individually for each local drive. You can enable them for drive C: and/or disable them for drive D: and/or enable them for drive E: and so on.
No, you would also have to switch off the OS message and set the recycle bin not to be used - both properties of the recycle bin are beyond the control of MP3tag and have to be set deliberately and on purpose by the user.
Even if MP3tag's behaviour should (ever) be changed, your system would stay just as dangerous for all other applications as those recycle bin properties apply system-wide.
So I would switch on all those options in MP3tag and the OS to activate all available safeguards when deleting files and then see if that is better for the workflow.
I would also add frequent backups to the workflow.
The recycle bin settings in Linux Mint have no impact on warning messages in Mp3tag. I always get a message - which one depends only on the setting in Mp3tag. How these correlations work in Windows could theoretically differ between editions. I have no clue if they do.
Probably, but not necessarily. It would be possible, although not likely, that other Windows editions differ in this regard. Which was my point, since the OP uses Windows 10 and his friend uses Windows 11.
Windows 7 settings
Windows 10 settings
... look both very similar to W11, I think.
That's not what I meant. Those settings may or may not affect warning messages in Mp3tag. In Mint/Wine they do not, so there's always some kind of warning. How this works in each Windows edition - in correlation with Mp3tag - is not yet confirmed.
Since you have Windows 10 & 11, why don't you test? I do think that you can confirm your assumption, that it works the same way in both editions.
He has the recycle bin activated normally. Strange
nah I was talking about disabling the delete function button; nothing to do with the os
This was already done earlier in the thread by several users. The warning messages appear as expected in Win 10 and 11, and with multiple versions of mp3tag up to the current latest beta. This assumes that in each local installation that the user has not intentionally changed settings for either the OS or mp3tag to bypass some or all warnings which could lead to these dire results.
Not from what I can see. Whether the settings for the recycle bin actually affect the appearance of warning messages in Mp3tag has not been confirmed for Windows 10 & 11. But it's probably so.
These are two different things. By default mp3tag pops up a confirmation request when the Delete... function is used. This can be changed in the options, but requires user interaction to make it happen. The OS setup including the capacity limits and function of the Recycle Bin are also user managed but are outside of the control of mp3tag. One way or the other, if the defaults are changed it is on the user at that point. Beware the Delete key and always be prepared for the consequences. And always have backups.
