I can second this, and he's not even my boss.

Also, just as an additional resource, the Vectorworks help files were updated for Marionette in 2017 to include two examples of network creation in Marionette. I designed the more advanced one which should help to show what you need to know. I believe this link should bring you to it. http://app-help.vectorworks.net/2017/eng/index.htm#t=VW2017_Guide%2FMarionette%2FMarionette_Tutorial_Creating_a_Simple_Cabinet.htm%23XREF_41117_Creating_a_Simple&rhsearch=marionette&rhsyns=

If you want to edit a script of a Marionette object, you can right click and choose "Edit Script" or sometimes you can just double click on it. (The only time it won't work on double click is if it is using control geometry, in that case you will activate the reshape tool.) Another option that I sometimes do is to "Convert to Wrapper Node" and then "Unwrap Marionette Network" so that you can see the guts right on the drawing area. It's easier to test this way because you can then just run the network to see the results rather than having to go in and out of the Object's 'guts' All Marionette networks are saved right to your drawing area (in the case of a wrapper/object, they are just in containers, similar to groups/symbols). Default Marionette nodes will reference an external Python file saved to your application folder, but in almost all cases you don't need to worry about that. For the most part, you should not ever have to edit the Python script in order to create objects/workflows with Marionette.

It will mostly depend on how well you understand objects in 3D space, such as their relationships with each other. After that, it's just making sure you wire the right nodes for the required math. Adding a back panel should not be too difficult, if you'd like some guidance, let me know.

Hey Alan! You and I should take the time to set up some records to simplify this even more at some point, that way you can create a report database without having to write the worksheet out yourself

I've put a new bug in for this since it's a little different than the one we have logged. VB-143687

Thank you! This appears file specific. If you copy that group into a new document and "flip" it, does it still break apart? In my testing it does not, but if you still see something it could have to do with your document setup.

A file would be super helpful because I'm not getting it to happen with my new file.

@Gadzooks Could you tell me what rotation the rectangle inside of your broken group is? As well as the original group that you tried to stretch to flip? EDIT: Also, as Kevin mentioned, a file with this object would also be helpful. Thanks!

We have a bug logged internally with regards to the reshaping of rectangles in this way. It's being worked on But thanks for sharing this! I hadn't thought of the impact in this way.

@NickSHere's the simplest script that shows how to place a symbol along a curve at equally spaced intervals, to get you started. The important thing is to ensure that your path is a NURBS curve. I'd be more than happy to give you further direction if you need it dupSymAlongPath.vwx

Hey Alan, When you're in a smaller screen size, you can get to the Marionette section by clicking the 3 Horizontal Lines button on the top right of the screen, that will open a menu that has the same links as the top bar does in fullscreen mode. Hope this helps!

I'll do my best!

There are others, but none that you should need to worry about. They're mostly back-end calls that Marionette uses on its own to make sure things are running smoothly. You likely won't find them floating around anywhere; DisposeObj() is only public because we use it directly in the code rather than DelObject(), etc. Most VS calls can be converted to Python just by putting vs. in front of them. Some VS calls won't work in Python, though, and some things won't work in Marionette because of how Marionette handles selection. The Developer Wiki is definitely the number 1 resource for what functions you can use with Marionette. You can also go exploring the base packages of Python 3 to add some functionality.

This is a special Marionette call that creates a list of objects to delete at the end of the script so that you don't try to reference an already deleted object in your script.