Pat Stanford

  • Content count

  • Joined

  • Last visited

Community Reputation

180 Spectacular


About Pat Stanford

  • Rank
    Vectorworks Addict

Personal Information

  • Homepage
  • Location
    El Segundo, CA, USA

Recent Profile Visitors

1,019 profile views
  1. I was hesitant to suggest this simply because I don't do architecture and certainly don't do multi-dwelling architecture, but at least for preliminary ideas, Design Layer Viewports could be a quick and dirty way to start, especially if all the exteriors were identical and you could simply draw one and reuse it in multiple DLVPs. It all depends on what your needed outcome is and the stage of the project.
  2. NURBS Curve, Polygon, Polyline, Arc, Rectangle, Rounded Rectangle, Line, Oval. are valid object types for profile objects. You can use 2D Polygons, 3D Polygons or NURBS curves for the path, but it will be converted to a NURBS during the extrusion so when you go back it will be harder to edit. If you think you might need to edit the path, you probably want to make a copy of the path object before you do the extrude so you can just redo it rather than try to edit the path.
  3. Draw the houses separately and then use Design Layer Viewports to bring them into the site model at the appropriate heights?
  4. I have not used events a lot. It is possible that the events are not powerful enough in VS/Python to give you what you want. Have you read the section on Vectorlab about events? There are things you can't do using events and VS/Python. From the above web page. My first thought for you wanting to check before and after states is that you will need to use a second set of hidden parameters. At the end of your script copy the actual working state parameters to the "Previous State" parameters. When you modify the object, these would then still contain the previous data and allow you to do whatever comparisons you need. Just don't uses the Previous State parameters anywhere in the script or expose them in the OIP. Based on my understanding either the ParameterChangedReset or ObjectChangedReset events should get you what you are looking for. HTH
  5. This post uses the Macintosh file paths. Very similar file paths are used on Windows. Search the help for User Folder if you have difficulty finding them. Note that the User:Library folder is hidden by default on the Mac. The default formatting for the schedules that show up in the Choose Schedule menu command come from the following file: Applications:Vectorworks 2017:Libraries:Defaults:Reports_Schedules:Architectural Reports.vwx You can just edit that file, but then you risk losing your changes when an update to VW is released or if you have to reinstall. Better is to duplicate the file to the following path. User:Library:Application Support:Vectorworks:2017:Libraries:Defaults:Reports_Schedules:MySchedules.vws You can actually name the file anything you want and edit the formats as you see fit to meet your needs. You need to restart VW in order for it to see the new file as part of the defaults. You will now get two versions of each schedule showing followed by the name of the file they are located in. If you don't want the original versions you can just move the Architectural Reports.vwx file out of the Applications Folder and restart VW. Let us know if you need more info.
  6. That's why I try to read everything on the board. You never know when an idea from somewhere totally different will make a huge difference to what you are doing.
  7. @bcd Nothing to be sorry about. You actually hit on the answer. With the Wall Insertion Mode off, the Duplicate works as Michael, Raymond and I wanted it to. DOH! Great solution. Procedure Test; Var H1, H2: Handle; B1: Boolean; Begin B1:=GetPref(581); SetPref(581, False); H1:=FSActLayer; H2:=CreateDuplicateObject(H1, ActLayer); HMove(H2,60",60"); SetPref(581,B1); End; Run(Test);
  8. I don't always Vectorscript, but when I don't that Python white space makes me cranky. Code Responsibly my Friend.
  9. I'll try. I'm on a Mac, so the exact paths on Windows will be different. I would move the file Detail Cut Wood.vso from: Applications\Vectorworks 2017\Plug-Ins to Pat\Library\Application Support\Vectorworks\2017\Libraries\Plug-ins. I think the destination path on Windows would be on Windows it would be by default the folder [userName] /AppData/Roaming/Nemetschek/Vectorworks/2017/Plug-ins It probably would be wise to double check that the file has User access permissions before you restart VW. You will probably need to update your Workspace by removing the VSO and re-adding it so VW knows the new location. The Detail Cut Wood.vso should then show up in the Plug-in Manager in the Custom Plug-In pane instead of in the Built-In Plug-ins pane. Edit the parameters just as you have before. Hopefully now the changes will be saved.
  10. There probably is and @MullinRJwill probably point it out to both of us shortly. ;-)
  11. A better option may be to use a worksheet. You can add columns for the parameters you want to be able to control. Edit the first one and then copy that cell, select all the other cells in the column and Paste. Kind of works like Fill Down in Excel. Scripts can work, but you will need to have either one script that changes all of the parameters or multiple scripts for each different parameter. And in order to make a change you will need to edit the script first and then run it. You could put in dialog boxes, but the time you spend writing and editing the scripts is likely to be more than the time to make the changes manually. Take a look at the following thread to find how to see what formulas you would need in a worksheet. You probably should read back through the thread to see what the script is supposed to do. Make sure you run the script with a window NOT In Wall as the only selected item in the drawing.
  12. Feel free to ask lots of questions. There are several of us who like to help newbie scripters. ;-)
  13. The following will toggle the crop on and off when you are in a perspective view. SetPref(127, Not GetPref(127)); Copy that line, go to Tool:Plugins:Plugin Manager. Click the New button and choose Menu Command. Click Edit Script and paste in the line above. Click OK. Click Close. Edit your workspace to include the new command. Let us know if you need more help.
  14. So why not do the copy paste in the script. It seems to work. If you want the new object to be In Wall, just use a SetParent. DoMenuTextByName('Copy',0); DoMenuTextByName('Paste in Place',0); Just so you don't feel too bad, I just spent 45 minutes coming to this realization. ;-)
  15. Most of the default plugin objects are transitioning from being Vectorscript based to being SDK based for better performance. Unfortunately, this greatly limits the ability of the end user to change the defaults. I am not certain if that is what is happening in your case or not. Your idea about permissions could very well be correct. Try moving the Plugin from the Application folder to your user folder. Use the same relative path and quit VW before you do the move. Then try and edit the parameters from there.