Hi!
After having a conversation with the mcneel tech support there came up the thought of changing the way of conversion of rhino v5 files.
Now there are needed some other user opinions for that to change.
Let me explain an example of how it works at the moment:
- you are working with cloud files of the team
- you’re accessing a v5.3dm file to collaborate, open it (in future) with Rhino 6 for Mac
- after making some changes to that file and saving, you’ll be asked if you would like to convert the file to v6. small fonted theres written that if youd like to save it as v5 you should do that via export.
- clicking on convert leads immediately to an unaccessible file for Rhino 5 users, replaced with the original file
INSTEAD of this workflow, I think it should work like one of the following two alternatives:
(1)
- open file from cloud
- change, save, dialog appears ‘would you like to duplicate and save as v6?’
- conversion works like that (automatically): duplication of the file youre working on > duplicated file is saved as v6 > you’ll continue to work automatically on the duplicated file
(2)
- open file from cloud
- change, dialog: save as v6
- instead of overwriting the file to v6 (standard) or duplicating (solution 1), you’ll be automatically redirected (solution 2) to the EXPORT window, giving the possibilities of export options you’d prefer.
In that way overwriting never happens by accident.
What do you think about that?
greetings,
Julian Botti