Why is there such a restrictive project file naming convention?
If you consider this convention too restrictive see it in the light of the project concept described here and you will notice that it is absolutely essential. It is not a result of programmer’s laziness but will save you lots of clicking around in file browsers because by adhering to this convention the program can much better guess at what you are trying to do. The only downturn, however, is that it is not possible to have several mark list files to one MP3 or several projects of the same name without losing project history support. If you start to manually rename files you will lose the history links and therefore face confrontation with the resulting prompts – and also risk a mix-up of wrong mark list files with wrong MP3 files and so on. In effect you will be getting in the exact situation that this project concept is trying to avoid. to index 4.6 I have an MLF without the corresponding MP3 and I can’t open it. What’s wrong? Nothing. This is a consequence of the project concept. If
