FileStp_Write feature wish

I’m super excited about the RhinoCommon API to write STP files. Yay! No more RunScript!

Wish: overload the Write method to take to take en Enumerable:

// Current:
public static bool Write(
	string filename,
	RhinoDoc doc,
	FileStpWriteOptions options
)
// Wish:
public static bool Write(
	string filename,
	IEnumerable<RhinoObject/Geometry> objectsToExport,
	FileStpWriteOptions options
)

You can use Headless RhinoDoc.

1 Like

Don’t think I can: Working with multiple RhinoDocs

headless doc wont show up in the UI. You will need to copy geometry from the active doc to the headless doc first. Don’t know if it fits your workflow

That’s exactly what I asked about in the other thread… that workflow seems much more logical to me. But apparently it’s not the recommended way to do things.

Do you do that in your plugins?

This is not true. You should be able to create a headless doc and fill it with whatever geometry you want in V7 for export. That said, doing this seems like a lot of overhead compared to your request for just exporting a subset of the current doc.

I added your request to our wishlist at https://mcneel.myjetbrains.com/youtrack/issue/RH-61227

Thanks for clearing that up @steve! I misunderstood the answer in the other thread. I would much rather do it this way.

Thanks for answering this for me @gankeyu!

Is there any chance of having an overload for FileStp.Write that uses a stream rather than saving to disk?