Jump to content

NeonClear

Member
  • Posts

    12
  • Joined

  • Last visited

Everything posted by NeonClear

  1. I would like to create a 2D polygon, set to layer plane, and then rotate the object to face the front view. I want a 2D polygon because I want to have color fills still work in wireframe. Does anybody have any ideas? I've attached a file where I show a 3D polygon in the orientation that I'd like and a 2D polygon (layer plane) that I'd like to rotate on the Z axis. layerplanepoly.vwx
  2. Okay, I screwed up and just had a typo in my folder structure. So this is totally possible, the custom plug-in doesn't have a limit on how many lines the script can have. So export the Vectorworks wrapper as a Python script and then copy and paste that script into the custom plug-in. Put that in the workgroup and then have your coworkers add it to their workspace. Yay!
  3. I didn't know that was possible! That works for several of my workflows. I'm trying to extend this a little bit further by making a custom plug-in. The custom plug-in works as expected locally, but I'm unable to get it to work via the workgroup using these instructions. Is this possible?
  4. I'm looking for some pointers on workflow here. I've made some Marionette scripts that are critical to my company's workflow. Many of these are commands that pull record information from the title block and then generates an email template (using a mailto: link) to update a team of people on the status. What is the best way to share these scripts with all of the people in my department? Currently I have a file in our workgroup folder with the marionette wrapper in a symbol and people have to drag the symbol into their document, run the script, then will often delete the wrapper. It's a few steps that feels a little sloppy, I'm looking for something that feels refined. Is there a way add to Tools > Marionette Commands from the workgroup? I want to maintain of control of updates to the script. Does anybody have a good way to convert Marionette scrips to regular scripts in a pallet? If I export any of my marionette networks they are way to big to use as a regular script. Edit: spelling.
  5. Ahhhh, the dangers of copy and paste. Darn it. Thank you very much.
  6. Fantastic! Exactly what I needed. Thank you so much!
  7. If I try either of those, I get "12.000000000000002" and not " 1'0" ".
  8. I'm working on a marionette script that can do the following Take dimension inputs. Make a shape base on those inputs. Make a text box next to the shape with the dimensions and other specifications. I'm having trouble converting the dimension value into a string. Does anybody know of an easy way to do this? Here's what I've tried so far. I've attempted to make a node for VS.Num2StrF but I'm not having any luck. If I hard code the value directly into the function it works. vs.Num2StrF(12.000000000000002) If I try to pass a variable, then it doesn't work. Am I making a simple mistake? vs.Num2StrF(self.Params.dim.value)
  9. That worked! So the band-aid fix is to add and remove that line each time I need to populate this list? I think I can make that work.
  10. I tried that and no change to the list of popups. I went one further and added #test as the last line of the node and saved it to see if that would refresh it, no luck.
  11. I'm having trouble with the "Set Layer" node, it never populates its list of the design layers in my document. I've attached a picture of my small example where my design layers are "Original" and "Transferred Here" but in the properties for the node my options are "Design Layer-1" and "Ham". Does anyone have insight on how this node is supposed to function? Also does anyone know how I can send an object to another design layer with marionette?
×
×
  • Create New...