Hi!
We mass print layouts to create pdf or png images to be used as linked images in DWG or InDesign documents.
When printing multiple layouts at once, it would be very useful if Rhino PDF could output single pdfs named as the layouts, instead or as an alternative of sequenced naming.
in printing as an Image the name of the layout is not brought to the “Save as” panel. It would be very useful if the file name is defaulted to the layout name, as it happens for single PDFs printing. Multiple prints should then behave the same as described in point 1.
a hierarchy system for the layouts would be very useful (grouping the layouts is really important in complex environment, like it’s done with the sheet manager in Autocad). Now we do it using “//XYZ” placeholder layouts but
Image printing should share most of the same UI logic as Rhino PDF. I hope to make this change for v9 since it’ll likely be a pretty disruptive and possibly breaking change to try in a v8 service release. Here’s a link to an existing ticket we made where Wim and I have had some of these same similar thoughts. RH-76439
That would be super nice to enhance Rhino’s productivity in a combined setup for Architecture/interior designers using Rhino/Autocad/Revit/Indesign etc.
We pass documents from one software to the other continuously. And we need to automate most of the functions because the process needs continuous interconnected updates.
Btw, I’ve been struggling also with scripting to make “-printer” work to output images but I am having issues. It seems that the Image printer is not managed correctly (can’t set a few parameters that I need, including the filename).
Yeah all of these things would ideally be fixed when RH-76439 gets implemented. Once that’s done there won’t be much difference between Image printing and Rhino PDF printing features.
Under the hood the two are treated as very different printers and that’s really not necessary anymore so getting them unified into similar feature sets is absolutely needed.
I added a link to this thread to RH-76439 so that I can reference back to it when I’m working on the implementation to ensure I don’t miss anything we spoke about. Thanks again for the feedback.
Travis,
What about adding the layout management/print capability to Grasshopper? Is anyone in charge of a possible feature there? Should I open another Topic to suggest it? I am actively using Rhino.Inside.Revit and layout/printing management in Architectural design context, considering also the new Rhino 8 GH panel seems auspicable.