On Tuesday, October 23, 2007, at 11:15AM, "Christiaan Hofman" <[EMAIL PROTECTED]> wrote: >I am confused about aliases to files that do not exist. This may give >problems for persistency of the new file objects. > >If a file does not exist, it seems that the data from the alias >becomes invalid. That is, if you save this data, and later try to >reopen it when the file has been restored on the proper path, it >won't be able to find this new file. > >Any idea why this would happen, and how to avoid this problem?
So the file existed when the alias was created, and was then removed, and the alias data was saved? If the alias was created with a relative path (or the absolute path didn't change), my understanding is that the original alias data would be valid. Trying to resolve the alias and update it between the time when the file was removed and the point at which it was saved could probably mess it up, though. I think we need to look into unit tests or something similar for this, and add test scenarios as we think of them. The problems are complex with relative paths, and the existing alias documentation isn't as helpful as it could be. -- adam ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bibdesk-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
