Marissa Farrell

I think this should be possible with some work, but unless I'm forgetting something, there's not a command that does this in Vectorworks, which is why there is not a node for it yet. edit: i take that back, obviously convert to group would work...

There currently is not one in our default content, but I think I have one floating around on my computer. If I'm understanding correctly, you want to insert a symbol object as a group? Generally this is just a setting of the symbol resource, but I can certainly get a network together that can take the contents of a symbol definition and insert them as a group on the drawing area.

Could you either post the file here or send it to me privately in a message? Thanks!

If you would only be using this version in one file, you can remove that #COMMAND... line and the node will continue to work fine. The #COMMAND... line is mostly for us internally because it allows us to maintain a versioning system for our node library.

Hi Ed, Which version and service pack are you using? I'll try to do some investigation, but in our internal PS/Marionette testing, I did not encounter this problem.

That message is expected. It's telling you it couldn't already find the file, but it will create it for you. Go ahead and continue through after that message and you should be all set!

You can use any local path you'd like, but yes, you should be able to use [UsrLib] for your user folder. I haven't checked in a bit, so if that doesn't work, please let me know and I can reevaluate. Also - to create the .py file, I would suggest creating your node in the script editor and then adding the command after you have it all figured out. It should look like this: #COMMAND;REFFILE;[UsrLib]/Defaults/Marionette/FolderName\FileName.py; Make sure you leave out the READONLY because it will give you an error when creating the file. You can add READONLY after the file has been created and it will update the file accordingly.

This is logged and confirmed a regression in our bug tracking system. VB-152252

If you have networks that run correctly in 2016, they should still run fine in newer versions. We've made a few changes to nodes, but mostly housekeeping, nothing would change the functionality of 2016 nodes much. Your 2018 nodes can be added to your old network without issues. If you run into any problems, feel free to send me a direct message with your file and I can take a look!

It's probably easiest if you start out with a defined record in your RM instead of creating it within the Marionette Object as you have in your file. You are off to a great start, though! Just need to plan out what the requirements for the object really are. My thoughts: Create record format with the fields you want to use Create symbol with a Marionette Object that reads the values from that attached record to define the shape(s) within (this would not be bi-directional with the Marionette input fields, only the record fields would be editable) Edit the Record Fields of the Marionette Object(s) you want to resize We *may* be able to do a bi-directional object, but I think that gets out of sync too often. We could also decide that instead of the Record Format defining the shape that the Marionette Object will update the fields of the record, but then you wouldn't be able to make corrections directly from a worksheet report. I have an object floating around on the forum *somewhere* that does something like this, but I haven't gone poking around to see if I could find it.

I'm looking into making this work. There are some commands that will return Viewport scale, I just need to see if I can get a Marionette object to work correctly inside of an annotation group. I'm trying to avoid inserting page based symbols because I can't guarantee their reliability. They would almost definitely require a manual reset. I'm running into a problem where Marionette Objects in the annotation group won't allow you to edit their contained script so it's taking a little longer than I would have hoped. We haven't tested workflows with Marionette Objects in viewport groups, so bear with me, and rest assured that I'm logging all of the issues I'm finding 🙂

You appear to already have 'Use at Creation' set. That setting is in the "Edit Class" dialog. It looks like you have that object set to use the class settings in the attributes palette which is why it works correctly. If you open the file where it hadn't been working, select the cabinet, and set everything to use class values in the attributes palette, it should also work. It's the manual way of doing what the "Set Fill Color by Class" node would do. Please let me know if I was unclear.

Looking deeper - it looks like you aren't setting your objects to use the class fill color. I've updated your network to do so using the "Set Fill Color by Class" node. Please let me know if you have any questions! Parametric cabinet_MFarrell.vwx

For your class settings, do you have "Use at Creation" set?

Thanks for confirming! I'll get it filed in our bug tracking system and see if we can get a fix.