by simonschouten » Sun Nov 26, 2017 6:22 pm
Hmmm - I'm not using Linux, I'm using Windows 10. I'd argue that MM should understand that a directory or file beginning with a dot would be taken as hidden in Windows, and therefore shouldn't need any further attention by a user, especially one with limited techincal tendencies, who'd not want to fiddle with .ini files!
Anyway, that said, I did some more analysis, and the issue is reproducible, as follows :
1. Rip a CD with leading periods/dots, eg ...And Then There Were Three.
No problem. It's there in your library, and MM has an explicit pointer to the directory ...And Then There Were Three, and the files within. If you look at the actual directory in Windows Explorer, you see it if you enable viewing of hidden files. So if you never have to do anything from there, no issues ......
The issue comes if you have to rebuild your library should the MM database become corrupt, or you have to reconstruct your MM environment for whatever reason.
I've just done that, and voila : MM has ignored it because it is a hidden file ........so I'd suggest this is a design fault which you only see if you rebuild your database?
Hmmm - I'm not using Linux, I'm using Windows 10. I'd argue that MM should understand that a directory or file beginning with a dot would be taken as hidden in Windows, and therefore shouldn't need any further attention by a user, especially one with limited techincal tendencies, who'd not want to fiddle with .ini files!
Anyway, that said, I did some more analysis, and the issue is reproducible, as follows :
1. Rip a CD with leading periods/dots, eg ...And Then There Were Three.
No problem. It's there in your library, and MM has an explicit pointer to the directory ...And Then There Were Three, and the files within. If you look at the actual directory in Windows Explorer, you see it if you enable viewing of hidden files. So if you never have to do anything from there, no issues ......
The issue comes if you have to rebuild your library should the MM database become corrupt, or you have to reconstruct your MM environment for whatever reason.
I've just done that, and voila : MM has ignored it because it is a hidden file ........so I'd suggest this is a design fault which you only see if you rebuild your database?