It would make the workflow for creating “Parts/Components/Development-Stages” much more efficient and practical.
Is this an OS limitation?
Respectfully,
Marco
Hi Marco - so, a sort of drag and drop ‘export selected’, if I understand your idea, is that right? What would you expect to happen after the ‘drop’, a file name UI?
thanks,
-Pascal
Hi Pascal!
Yes. A file name UI is probably the only thing that would make sense, especially if we drop multiple objects where would be impossible to assign, by default, their Properties Object Names, if any, or ID numbers.
Regards,
Marco
Hi Marco - do I understand that with multiple objects dropped, you would expect a file per object and not a file with all objects? Also, would you expect to be able to specify a format other than 3dm?
My guess of the moment is that this is probably not hard but unlikely to get into the V6 release… nevertheless I’d like to get it on the heap…
http://mcneel.myjetbrains.com/youtrack/issue/RH-33203
thanks,
-Pascal
Hi Pascal,
the format other than 3dm is less frequent and the Export command would be my first choice (Export Options, Dedicated Folders etc.) but regards to the Multiple vs Single is a good question.
Since I use a combination of both during development and sharing, I would wish a Modifier Key for the choice when dropping the object(s).
Thank you for interest in the subject.
Marco
Hi Pascal,
Just adding a comment in the event that this feature gets implemented.
After dropping the object(s) into the library area it would be impractical to have Rhino asking to export each individual object and save each one separately.
Imagine I’m dropping a group of 20 or even 100 grouped objects!
A simpler way is to just use the standard Export function as one single file and just popup the saving dialog with the current open file’s name highlighted in order to add an extension to it or just type in a new file name altogether.
This could really help in my industry workflow.
Thank you.