Clement,
Re:
using the document path should be fine as it is unlikely that you get more than one file with the same name and path.
This is not ideal. For instance. A user makes a file, produces some geometry / work, and then saves it to a directory, maybe even their desktop. The file might be given a project name - ‘newyorktimes_renovation’. Then, they or someone else might then move this file to another directory manually when they chose to clean up their desktop.
Note:
- The link is broken - it’s broken because the path has changed.
Then…
What happens if the user then comes in to work the next day and builds a new file. They call it the same name (because it’s the same project) and they also save it to the desktop - because it’s a bad habit they’ve gotten into (like all of us have)?
If using path data this new file is then determined to be the same as the former file - yet it could be quite different and it certainly is a different file.
Note:
2. The link is now not just broken but also in error because it is associated with the wrong file.
Clearly a unique GUID would be better.
How to solve the copy problem:
- If a file is copied, say cut and pasted in the file system, it would have the same guid as the former file, this is true. I haven’t thought about the solution to this problem and their might not be one at the level of Rhino - this is seems to be an OS issue that needs an OS solution. You are right here.