Marissa Farrell

This will show the period as the separator.

This file might help you a little, there is still the case of changing the thousands separator from "," to "." I'm trying to decide the best way to replace the comma with the period, but it's a start.

Oooh! That could be cool for confetti or pom-poms!

I'm not seeing your solution work, but maybe I'm missing something. I also think it wouldn't be optimal for the case where you want to mirror across a different axis. EDIT: Nevermind. I do see a possible use for this. I had to change my case to (-1, 1) though, due to the shape I was mirroring. But I'll still have to look into obscure angles.

I don't think there will be a fix for it in 2016. I tried writing a workaround, but haven't been successful.

Definitely not too much for a Friday! Helps brighten the last few hours of this week

Have you looked at your settings in the Create Symbol dialog? There is a checkbox that offers the option to convert 2D objects from Layer Plane to Screen Plane, if that option is checked, the 2D object should be created as a 2D symbol.

I think this has to do with Hybrid Symbols. As an example, draw a circle and a rectangle, select both and create a symbol. (EDIT - draw them on the layer plane, but keep the option to convert 2D objects from Layer to Screen plane in the Create Symbol dialog) Edit the 2D symbol and change the circle from screen plane to symbol definition, it will alert you that you're now creating a hybrid symbol. When you exit the symbol container, you'll notice that the circle will now display in 3D views, and the rectangle will appear in Top/Plan. Maybe this can help clear things up, at least a little, as to why this occurs.

In addition, if it IS a group/symbol/container object, you may also want to call GetParent on it to see if it's a child of ANOTHER group/symbol/container. (If it returns a Layer, then you're at the outermost container object)

What if you check the type of the object you're querying to see if it's a group or a symbol or another object type that could qualify as a container? That should let you know if it will have any "children". Still a little clunky, but I'm sure there aren't many other object types that would qualify as a container.

Currently, I don't believe that we've discussed providing objects, other than those that are being shared on the forums. There is no plan in place to release any Marionette objects within the software. I agree with Martyn, though. So far the members of this community have been great in sharing what they've learned and helping others along when they get stuck. I would also agree that describing what you want the results to be specifically will greatly improve the chances of help. I pretty much hawk over the Marionette forums and help wherever I can. I do sit back, however, if someone else has input (because I think learning from everyone is very important, and I want everyone to have an equal chance to communicate his/her thoughts on methods of creation)

Currently, in 2016 (all service packs, to my knowledge) if you change the preferences BEFORE inserting your bridge line object, and check the "Set Cover Weight Manually" checkbox, when you draw your bridge line object, there will be an option in the OIP to set the weight. I did throw it back to the engineers to have that setting persist regardless of the settings when the bridge was drawn, hoping it will always be included in the OIP. But at least for now, there is evidence that it has been (partially) implemented.

We also had a mishap with the default setting of the Marionette forums to only show posts back to a certain time frame. We updated this (a few months ago?) to show all posts from as far back as they exist, so it may have slipped by that way.

Attached is a file with an explanation of how lists work with Marionette as well as a way to manipulate them to behave how you would like. The trick here is using the "Mix2" node. It is a very powerful node that is often overlooked, but also very important for cases like these. Please don't hesitate to ask any questions.

This is because of the logic Marionette uses with lists. I'll try to provide a working example and explain the situation shortly.

Remember, Alan, I only have it working in a Marionette Object, I can't get it to work if I just run the script!

Here's a file with an example. I'm still not fully comfortable with the process involved, so I might not be super helpful if you have questions, but I can try. I have noticed, though, that this only appears to work if it's in a Marionette Object, it's been failing on me if I just run it as a network or wrapper. I'll be sure to look into it. I modified the currently existing Surface from Curves node to accept an input of curves, in this example I only used one. I don't know how it would work if you did more? Again, this procedure currently is over my head. I can TRY to answer any questions you may have.

I think it needs to be touched up. I don't think it was implemented correctly. Give me a bit and I'll try to update it/produce an example for you.

There was this post from a while back, for one reference.

Hey Alan! Thanks for bringing this up. I, too, have been encountering the problem when converting to Polygons. It appears that some shapes when converted are actually being created as MULTIPLE polygons (you can think of it as each line is now a separate object) and we don't have a "compose" node to fix this problem (something I'm working on, I promise). I'm not sure what the circumstances are that the conversion fails, as you and I have noticed, it DOES work in some cases, but fails in many others. You're not doing anything wrong. We just have something weird going on with the back end of all of this. I'll look into it further. Thanks! Marissa

Benson, You express the exact sentiments I have about making videos. It's hard to find the right time and place to create demonstrations of things, as well as making sure that you can represent your work in an understandable fashion. (I also, as many others, fear hearing my own voice in playback.) Hopefully you, I, and all others with talent/things to share can get on top of it and start sharing our demos, greatly enhancing Vectorworks' user community.

So here's as helpful as I can be at the moment. I've mocked up an example using a Hemisphere and contouring to produce "shelves" throughout it. (you'll have to use your imagination on the shelling of the hemisphere ) Your output will be a little trickier, as you have a more difficult contour result. I would suggest attempting to add a vertex on each poly (after converting from your NURBS) to prevent the crossover you'll probably encounter. If I wasn't descriptive enough here, feel free to reach out to me directly (either through a message here, or by email - which you can find in my profile)

You'll most likely want to leave "dir" alone, the default value will split the surface horizontally. I'm having a hard time producing an object that will extrude, though. Usually when we use contours, we use it on an object that would produce a closed shape, in this case, it's not really doing that well since you're just doing a surface that was converted to a generic solid. I'll keep poking it, but I feel like this workflow is probably not going to produce the results you want.

I don't think there's an 'out of the box' function in Vectorscript to do a projection, which is why the node you're looking for probably doesn't exist. I don't believe you're missing anything. I'll add it to something we should look into, though!

Okay, I've just encountered this with a wrapper I had previously created. What's the name of your wrapper, as well as the name of the symbol the wrapper is stored in? Do you have any other Node/Wrapper with the same name? I think mine is due to having both a Node and a Wrapper in the Marionette directory with the same name, but I haven't investigated entirely.