Marissa Farrell

@Pvz11 You can move your Extrude Along Path upward using the Move node, or you can extrude legs below the EAP. Once converted to a Marionette Object, it can move around freely. The Marionette Object has its own coordinate system that you will use to move/place your individual parts.

You can create your profile the same way I got around the compose issue - determine the location/drawing order of your vertices and feed them into a Poly node. Using the Ordered List node allows you to order the points that are going into the Poly node, if you were to just wire them all into the same port, the Poly node could take them in unpredictably. Ordering them ahead of time will ensure that they are drawn exactly how you expect. For example, a square profile - you would provide it 4 points (0,0), (0,1), (1,1), and (1,0) into the first four ports of an Ordered List node, placing a Polygon 2D node after it. You then have two options; you can use the Set Closed 2D node after the Poly node, or you can wire the first point, (0,0), into the fifth port of the Ordered List node (item4). I hope this helps, but if it doesn't, feel free to keep asking for clarification 🙂

@Pvz11 I took a look and made a few changes to your network - I didn't edit the one you have on your drawing area, but I did redo the one inside of the Marionette Object. I hope this helps - basically the "compose" node was failing to compose the lines while in a Marionette Object, I'm going to submit a bug for that since I'm not sure why it works in a regular network, but not in an Object. Please let me know if you need any help improving this further! Marionette-ExtrudeAlongpath-OfficeDeskCounterTop_MFarrell.vwx

Attached is a file with a revision that should work for this use case, I'm sure there's a reason I didn't go this route initially, but I can't recall why. There's also a chance I had fixed the issue you're experiencing in a more recent node, though I'll have to dig through some files to see what my latest revision was (though I'm sure it's more recent than Nov 2018, as dated in the node you've been using) Tags_to_Designlayer_List_MFarrell.vwx

Hmmm. This should be running correctly, there's nothing wrong with the code that I'm immediately seeing. I'll look into this.

I've been using MagicPrefs for a few years now while testing on Mac with the Magic Mouse. It was a game changer for me.

There's not a traditional method of looping in Marionette, but if you incorporate the Sequence/Range/Series nodes, they can help to facilitate behavior similar to a loop. Take a look at those, and if you need some guidance let me know and I'll try to find some time on Monday to help guide you 🙂 This will just be a matter of list manipulation, so check out all of the Data Flow nodes.

I think the best way to get started is to script something you already know how to make WITHOUT scripting. Write out a list of the steps you take when drawing something, and then look for nodes/functions that would help accomplish that for you. For Marionette, if you aren't able to find a node to do something, ask in the forums; sometimes it's been created but not added to default content, and other times it can be made for you quickly. Start small and build from there. If you want to do something complicated, try doing the smaller parts of it first and then expand on it.

One approach that I can think of is to create multiple square grids and offset (move) some of them to give you the appropriate points for an isometric grid. I'll try to find some time to experiment later, but maybe that can give you a head-start on me towards a solution 🙂

I'm attaching an example to get you started - it still needs some error handling and modifications to get exactly what you want. I've added a new layer for the Control Geometry example, and I've modified your original network on its original layer. Let me know if you have any questions! CIRCLES IN CIRCLE_MFarrell.vwx

Great question! Ungroup will actively ungroup a group (unless it's a group created by Marionette) and return the handles of the objects that used to reside within it Contents will give you the handles to the objects within a group without ungrouping it. Generally, they can be relatively interchangeable if you don't really care about the grouping of objects in the end, but in this case (though I'm not totally certain) I believe it fails because once you ungroup the objects in a Control Geometry container, the node that references Control Geometry doesn't know what to do anymore since it's only supposed to contain one object (ungrouping would result in the Control Geo container to now contain three separate objects). I hope that helps to clear things up at least a little bit!

I would suggest instead of using the Ungroup node, use the Contents node. I've attached a revised file. ExtrudePath_MFarrell.vwx

The chunk node *does* work on curves, the issue is that the Divide Curves node does not understand how to use that input. Here's a network that I think accomplishes what you're looking for. What you'll need to do is just approach things a little differently - manipulate your lists later on when they're not objects and are instead point data. I included valves at the end to show you different results - when you just generate curves, you're missing the last point which doesn't give you a closed curve. The easiest way to circumvent that is to first create closed 3D polys then convert to curves afterward (You could, of course, manipulate the points instead as you did in your wicker file.) example001_MFarrell_v2.vwx

I'm attaching a simple example - hopefully it will help you better understand the Chunk node. How the Chunk node works - you provide it a list and an integer. The integer represents how many elements you want in each list, in my example (based on your example text), I want 10 elements in each list. The output is 5 lists of 10 items. Marionette_ChunkingLists_MFarrell.vwx I also modified the network in your attached file to update it to what I *think* you wanted to do. example001_MFarrell.vwx Also - I do hope you'll give me my bonus points 😉 The handle types can be found here: http://developer.vectorworks.net/index.php/VS:Function_Reference_Appendix#objects