Hi,
Probably unfair to call the following a bug - as it's behaviour that seems correct in the context of a purely local filesystem. However, it can catch you out if your Project contains references to remote files.
It went like this:
1/. Create a deeply nested Project file, consisting solely of pointers to files on a remote disk (mounted via SMB). 2/. Do work, close Project file. 3/. Eject the SMB drive. Go to lunch, or whatever. 4/. Return from whatever and reopen the Project file - forgetting to remount the remote disk first ... 5/. Gaze in silent horror at the empty Project.
On start-up, TM silently deletes all unresolveable file references from the Project, leaving only the Groups that you have created. Any laboriously constructed filter definitions are deleted too, of course. TM immediately writes the revised Project file back to disk, making sure that you can't recover from your mistake.
Might it be an idea to have TM pop up a warning - if it detects that a remote volume has disappeared?
On a machine left idle for any length of time, 'sleep' can cause remote volumes to eject themselves - so I guess TM would need to check this periodically, and not just at start-up.
Cheers, -- Andre
On 14. Oct 2004, at 0:36, Andre Posumentov wrote:
Probably unfair to call the following a bug - as it's behaviour that seems correct in the context of a purely local filesystem. However, it can catch you out if your Project contains references to remote files.
When I revisit the project drawer code I'll make it so that it only makes missing folder references red (as it currently does with missing files) instead of dropping them.
Kind regards Allan
On 14 Oct 2004, at 09:42, Allan Odgaard wrote:
On 14. Oct 2004, at 0:36, Andre Posumentov wrote:
Probably unfair to call the following a bug - as it's behaviour that seems correct in the context of a purely local filesystem. However, it can catch you out if your Project contains references to remote files.
When I revisit the project drawer code I'll make it so that it only makes missing folder references red (as it currently does with missing files) instead of dropping them.
Ah! I hadn't spotted the way TM handles missing files - all my remote refs have been to folders. So a good workaround for the moment is to manually create the remote directory tree as a collection of Groups, and then drop the files into those groups. Works perfectly - you can re-attach the remote volume after launching TM, and it promptly reinstates the missing files.
Good stuff - many thanks!
-- Andre
-
Allan Odgaard -
Andre Posumentov