Jump to content

Peter Vandewalle

Distributor
  • Posts

    317
  • Joined

  • Last visited

Everything posted by Peter Vandewalle

  1. This worksheet script may help you to find the data from a list. It works like the vlookup function in most worksheet softwares. WSVLookup.zip
  2. You could combine GetPt(x, y) to get the pickup point, h := PickObject(x, y) to get the object. GetPt will also activate the target cursor.
  3. JBenghiat's reply is the answer to your question..
  4. Or create a dim, real or integer field, full with SetRField and lock with EnableParameter (I think)
  5. Sure, you can just add a fixed text field and fill that with the SetRField command.
  6. You need 2 png files: - a 52x40 called <whatever>@2x.png - a 26x20 called <whatever>.png
  7. Any news on 137206? Roof textures by class not working.
  8. I do have a find replace in symbol name command. I would line to externe it to the level you’re requesting.
  9. Sorry, I forgot to upload the latest version of the VLookup script. I'm attaching it now. The beginning of the script contains the example line to insert in a worksheet: =RUNSCRIPT(120; 'Rapporten Architectuur/WSVlookup.py'; A1; 'A1..A5'; 2) You can change the formula to: =RUNSCRIPT(120; 'WSVlookup.py'; A1; 'A1..A5'; 2) Where: 120: path to script folder (Library:Defaults:Reports_Schedules) 'WSVLookup.py': script file A1: Reference to the lookup cell 'A1..A5': Reference to the lookup range, you can reference to another worksheet using 'sheetname:A1..A5' 2: Column number to return WSVLookup.py.zip
  10. Commands can only be in a menu, objects can only be in a palette. Commands and objects (like in parametric objects) can be created via the plugin editor, check the "extra" menu.
  11. To write back you can also use vs.SetRField(str(yourvalue)) str() is the Python way of turning a value into a string.
  12. Is there a way to get the height of a 3D volume at a given x, y location? What I need is a way to get the top Z height - bottom Z height at a given x, y position. Any idea that could help is welcome!
  13. After creating the marionette node, turn it into a symbol with the "convert to parametric object" option on. This way the node will become a "red" symbol. To create a category, just create a symbol folder and move the node symbol in there. To add your own nodes to the default library, insert it into a Vectorworks file and store that file in the (user) folder "Users/<username>/Appdata/Roaming/Nemetschek/Vectorworks/2018/Libraries/Defaults/Marionette/". Update you library and you're done.
  14. We’ll need the Vectorworks file to be able to solve this issue.
  15. Select all trusses and add solids first. Then intersect solids.
  16. The from data is in spreadsheet cells. I didn't need it from database rows... Sounds interesting though.
  17. I only used it in a database row. But I think it should also work in a spreadsheet row. Thanks for the manual!
  18. I recently created my own vlookup function. See attached file. Check the remarks at the beginning for the way to use it. WSVLookup.py.zip
  19. Split levels can be done by stories. I usually create multiple story levels for each level type: top of structure finished floor s_top of structure s_finished floor ... Then I create multiple wall styles: base to base, split to split and if needed base to split and split to base. Same for floors.
  20. I'm trying to create a kind of benchmark that could also modify the Story levels. I can do that, but then the section viewport needs to be positioned so that the origin of the model in the viewport matches the origin of the sheet layer. I'm trying to modify it so that it would work also when, the section viewport is positioned elsewhere on the sheet layer. I have been thinking about the elevation benchmark tool, but I can't read the indicated height value from the PIO object, there's no parameter for that...
  21. Hi Boh Doesn't work. Copy-pasting a 3D locus into a viewport annotation isn't possible. Copy-pasting a 2D locus will paste it onto the origin of the sheet layer inside the annotations. No luck so far...
  22. Is there a way to get the origin of the model in a section viewport? Since the Elevation Benchmark Tool is able to create a value based on the Z-origin, I suppose it should be possible. I just can't seem to figure out how...
  23. It's pretty hard to see what's wrong without the vwx file...
  24. I'm trying to modify the story level and update the viewport in one script. I think the modifications to the story level are effective only after the script has ended. So the viewport update doesn't return the wanted result within the same script. If I run the script twice, the viewport will update... Too bad.
×
×
  • Create New...