When you drag the package Testproject.ctp onto the CT interface, CT will create a folder "testproject" with the corresponding file(s). But if there is already such a folder and such a file, CT will neither overwrite the file nor give any warning. So if you do not pay attention to the stats, you will work on an elder file version (or maybe even the wrong file).
This scenario might be rather probable for anybody who works with CT on two machines and moves its resources as packages over the network/cloud, or maybe for anybody assigning CT packages with the same or similar names to someone else (much less probable, I admit).
tre
When you drag the package Testproject.ctp onto the CT interface, CT will create a folder "testproject" with the corresponding file(s). But if there is already such a folder and such a file, CT will neither overwrite the file nor give any warning. So if you do not pay attention to the stats, you will work on an elder file version (or maybe even the wrong file).
This scenario might be rather probable for anybody who works with CT on two machines and moves its resources as packages over the network/cloud, or maybe for anybody assigning CT packages with the same or similar names to someone else (much less probable, I admit).