Jump to content

Marissa Farrell

Marionette Maven
  • Content Count

  • Joined

  • Last visited

Posts posted by Marissa Farrell

  1. You need to take it one step further. Right click on the wrapper node and select "Convert to Object Node"

    That will create an object based on your script with editable properties in the OIP.

  2. Are you familiar with Marionette Objects? They would be your solution.

    Right click on your network and choose "Wrap Marionette Network" and then right click on the wrapper node and choose "Convert to Object Node"

    That will give you an editable object on your drawing that will behave like a Plug In Object. You can save that as a Red Symbol in your document.


    In order to display the parameters you want editable in the Object Info Palette, select those nodes and name them in the upper part of the Object Info Palette.


    Please let me know if you need any help 🙂

  3. 22 hours ago, Markus Barrera-Kolb said:

    Do you know if there's a way to print out a summary of the customizations


    Workspaces are stored in your user folder as .vww files, which are essentially .xml files; you could probably poke through there to check customization info, though it won't be so user friendly.

    It's likely possible to write a script that could make it more readable, but I don't have the time right now.

  4. 1 minute ago, zoomer said:

    Unfortunately again the typical super NDA stuff.



    1 minute ago, zoomer said:

    Is there a way to repair them (for you) ?

    And are there any other, hidden files, with known potential to corrupt,

    in our User Folders, which will be only be rebuild after the whole

    No automated repairs, all by guess and check.

    There's no real way to know which file(s) are causing the issue, to my knowledge. My approach is usually remove one folder at a time and relaunch until I find where the culprit is and then try to diagnose from there.

  5. 15 minutes ago, zoomer said:

    Just opened VW by a File from Explorer,

    - empty OpenGl 3D view

    - yellow rulers

    - just a single 12345e52637 number instead of ruler scale


    Last time I ran into this, it was a corrupt file.

    Can you send me that file privately?

  6. You could create a script in your Resource Manager (set the language to Python Script from the drop down) and place this code in it:

    def ResetThem(h):
    vs.ForEachObject( ResetThem, "SEL = True" );

    This script will reset all selected objects.


    Another option is to create a set of scripts that reset objects based on criteria, for example, the following script will reset all Space objects:

    def ResetThem(h):
    vs.ForEachObject( ResetThem, "((PON='Space'))" )


    You can also add these scripts as menu commands using the Plug In Manager.

    • Like 1

  7. Here's my progress so far -

    The Focus Points no longer end up in a nested group, though the LDs are still selected. I tried using the Set Selection node, but unfortunately that's not working for some reason (looking into it). This also fixes the issue where they are not immediately selectable.

    I did filter at the beginning of your network so that only LDs are queried, you/we may need to adjust the criteria for filtering because I'm not positive that my criteria is always true (I don't often look at the records of LDs.)

    I'm also going to look into some error handling for the naming, as I've mentioned above.


  8. I'm looking at this now and trying to diagnose some of your issues, but I wanted to make a quick note about when you're naming your Focus Points.

    If you re-run this network without deleting the focus points created on the last run, the names of these objects may end up incorrect (they will be incremented by one)

    I would suggest doing some handling for this because the lighting devices may end up pointing to the wrong FP after this happens (at least it did in my testing).


    I'm not sure why these objects are being created in a group/unable to be selected immediately after this brief examination, but hopefully I can figure it out.


    I've also begun adding filtering after your Objs by Criteria node to sort out objects that are actually lighting devices rather than allowing focus points to also be queried. I'll share my revisions once I make more sense of your other issues.

  9. There's not currently a way to automate the running of individual networks in a particular order, my suggestion would be to connect these networks together, possibly with pass nodes. 

    I'll try to mock something up once I find some free time as an example.

  10. I am going to say yes, but the time to produce something like this will vary based on how complex the objects are/how they are being defined/etc.


    Do you have an example of the outcome you're hoping for with variations?

  11. Here's a short network that returns these values.

    Often, values for Parametric Objects are stored in hidden records - this demonstrates how to extract the ones you've asked for.

    Record fields are returned as strings (text), so they will need to be converted to numbers if you plan to use them elsewhere.


    If you want to assign values to the object, you would instead use the Set Record Field node.




  12. @Thomas Gillioz

    In 2019, the Objects by Criteria node has a button below it allowing you to define the Criteria using a dialog.

    When I placed a column in my document and used that button, I was given


    as my criteria.

    If you are not seeing the button in the Object Info Palette with the Objs by Crit node selected, please replace the existing node with a new one from default content.


    Screen Shot 2019-03-11 at 10.12.02 AM.png

  13. If you're referring to a tool in a tool palette, you can sometimes click-hold on it to see other tools. (The tools with other items "sitting" below them are identified with an arrow indicator - tools named by text will have an arrow pointing right at the end of the text, tools with just an icon will have an arrow in the lower-right corner.)


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.