Which rhinoscriptsyntax functions do you need to have implemented next?

Updating the compiler is on my 6.1 list. This doesn’t necessarily mean that it won’t happen until 6.1, it just isn’t necessary to be completed before shipping an initial release of 6.0.

In other words, it is on my short list

This is a project that I would love to see get started. It seems like we could make an open source module that wraps up Eto functionality and exposes it in an easy to use in a ‘pythonic’ way. Docking dialogs specifically are going to be tricky and will require some changes in Rhino first.

Thanks @stevebaer. Does that mean that once the compiler suppors python modules this will work in Rhino 5 too ?

Me too :wink: Is it possible for Winforms too or exclusive with ETO ?


I don’t see why not at the moment, but I haven’t gotten into the nitty gritty details yet.

I guess it all depends on how such a module would be put together.

@stevebaer, this would be really great as i almost abandoned compiling my scripts once modules are involved.


I’ve mentioned this in the past, but it’s probably worth repeating now that this the Python functions are being addressed. Can we have the various listbox windows remember their previous locations? If I recall correctly, PropertyListBox is the only one that will open in the last place it was closed. All of the rest revert back to the top left side of the screen.

I found my old post on this subject:



Reported RH-41351

7 posts were split to a new topic: Sort and arrange order of layers programmatically: request

Is there already a way to use ViewCapturetofile in rs? I’m just about to look into using this in python.

Hi @siemen

Just script the ViewCaptureToFile command using rs.Command.

– Dale

RH-41282 is fixed in the latest WIP

1 Like

I would like to see rhinoscriptsyntax functions for splitting and trimming surfaces using a curve (or curves) on the surface (instead of using a brep as is used in the SplitBrep() and TrimBrep() functions). The functions could be something like:

SplitSurfaceByCurve(surface_id, curve_id)
TrimSurfaceByCurve(surface_id, curve_id, point)

Where surface_id is the guid of the surface to be split/trimmed, curve_id is the guid (or list of guids) for the cutting curve(s), and point is a 3d point on the surface indicating which portion to delete during trimming. The SplitSurfaceByCurve function wouldn’t have to be much more than a wrapper around the RhinoCommon Brep.Split method, but would hopefully be easier to use for those who aren’t as familiar with RhinoCommon.

1 Like

Reported: RH-41493

Late to the party here, but @piac I do not see rs.IsExtrusion anywhere… Thx, --Mitch

Thanks, reported: RH-43346.

Adding to the list:


Thx, --Mitch

Hi Giulio,


Also please have a look at this:

I am no longer in charge of this, but I reported these:




Giulio Piacentino
for Robert McNeel & Associates

Bump on rs.ObjectTopGroup…

First asked for here in 2014


Hi Mitch, Fyi, I added the function and some notes to the YT item

Thanks @Alain ! (I understand the limitations of this function, yes…)