![]() With little effort, I can add another drive inside a Mac Pro to allow for multiple local copies with a retention period, but I can't repair a corrupt file. The check-in/out system will track where files were opened and default to resubmit back to the same location. A failed submission back to server wouldn no longer matter the user still has their local copy, untouched. Preferences could allow for where to save the files and maybe even how long to keep these copies for. So we no longer are working with a temporary local copies that are deleted immediately after a save, but actual visible copies. At some point, inside PS, you may choose to resubmit (copy the files back) to the server, keeping the local copies. What I'm suggesting is PS having the ability to save the files locally for you and all subsequent file use and saving is handled locally. I would suggest that maybe the best solution would be a good check-in/check-out system inside of Photoshop and I'm not talking about one that file locks, this just unnecessarily complicates the situtation. As Chris suggests this is an OS bug, I can understand how it can be incredible hard to work around this with an effective solution for a software provider. Over the years, across different version and file servers (all of our servers are nfs automounts), we have intermittently seen file corruption and we all know how frustrating this can be, I believe Chris is as frustrated as us and putting this issue to bed would be fantastic for all. First of all, I personally would like to thank Chris for his continual patience with this topic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |