It seems we are discussing different scenarios and I’m not expressing myself clearly enough. Here is how the problem could be tackled:
- computer 1 opens the file, an .rhl file is created
- the .rhl file is propagated through Dropbox to all computers
- when user on computer 2 tries to open the model, the .rhl file is spotted and the model is opened up in read-only
Obviously, there are intricacies with how to deal with delays, asynchronous operations, and unreliable internet connections, but still - the above is what I would expect. If the model was sitting on a shared file server, one would expect this, no? If not, what is the purpose of the .rhl file?
What would also solve this issue is that I could simply quit Rhino/close the file and the original file that was opened is just left in the exact state it was when it was opened.
I’m telling you again - when I close my file and say “Revert Changes”, it does not simply close the file and leave the original there. It puts back a fresh copy of it that looks like the original.
Of course! As expected. He does save the changes.
Of course!! As expected. But with the added bonus of my colleagues changes also being overwritten by my copy (that Rhino writes back on disc) with the original version.