Jump to content

Pat Stanford

  • Content Count

  • Joined

  • Last visited

Community Reputation

590 Spectacular

About Pat Stanford

  • Rank
    Vectorworks Veteran

Personal Information

  • Homepage
  • Location
    El Segundo, CA, USA

Recent Profile Visitors

4,459 profile views
  1. Pat Stanford

    Vectorworks Fundamentals - Dimension error

    In the top set of options in the gear dialog options, choose the top option Use Floating Data Bar and let us know if that does what you need.
  2. Pat Stanford

    Vectorworks Fundamentals - Dimension error

    Please go to the right end of the mode bar and click the gear icon and send us a screen shot of how you have those settings set.
  3. Trying to use VW the way you used AC will likely result in great frustration. There are just too many differences. You need to accept that you will need to learn to do things in the VW way. As Mike says, Snaps are basically the same as your loci. You can set them to provide end/mid/intersections or even a random division. By hovering over an object you can see little tick marks that are the current snap points. If you grab and drag the point on an object you want to move you can then "read" the snap points and put it exactly where you want. You might also want to check out the help files on the Snap Box versus the Selection Box of the smart cursor. This determines how close to a snap point you have to be to get it to snap versus how close you need to be to get it to select. You may also want to read up on the Snap Loupe to let you temporarily zoom in to make a selection or pick a point.
  4. Pat Stanford

    Counting Plug-In Object

    Joshua is correct. As always. But perhaps a little more detail will help. The =N returns the Name of the object. This is the name that you can type into the OIP. I think it also returns the "source" object for PIOs and Symbols. VW is very picky about names and only one object in a file can have a specific name. You can't have a class named Door in a file that has a Door object in it. Your script retuned 1 because there is only 1 object with that name in the file. It is the definition of the PIO. PON to return the plug-in name or S to return the symbol name are usually better options for criteria.
  5. Pat Stanford

    What are these view boundaries?

    It used to be the only way to do a perspective view before Viewports. Now the viewport boarder basically acts as the crop object of a perspective view. But it is still available if you want a limited perspective on a design layer.
  6. Pat Stanford

    Script issue

    I kind of guessed that might be the case. Keep asking and we will keep trying to help you out. But response times might be longer than what you got this morning. ūüėČ
  7. Pat Stanford

    Script issue

    PushAttrs; TF:=GetCustomObjectInfo(ObjName,ObjH,RecH,WallH); CurrentCl:=ActiveClass; FillBack(256); FillFore(257); FillPat(1); PenPatN(2); PenSize(6); PenBack(256); PenFore(257); PenPatN(2); The above lines store the old attributes settings (Push Attrs) and set the attributes that objects drawn during the execution of the script will use. The PopAttrs at the end of the script returns the settings to what they were before the script was run. If you really want to use the class attributes, everything from FillBack to PenPatN could be deleted. IF (PBuildMat = 'wood 1 x 3')|(PBuildMat = 'wood 1 x 4')|(PBuildMat = 'wood 2 x 4') THEN BEGIN FillFore(46529,34664,22800); {0=black} FillBack(46529,34664,22800); {65535=white} END ELSE BEGIN FillFore(52428,52428,52428); {0=black} FillBack(52428,52428,52428); {65535=white} END; These lines control the color that the fill is set to. If you want to use the class attributes you could eliminate the IF/Else and just use SetFillColorByClass; IF TF=True THEN BEGIN NameClass(CMClass); SetClLSN(CMClass,2); {Line style} SetClPenFore(CMClass,0,0,0); {Pen fore color} SetClPenBack(CMClass,0,0,0); {Pen back color} SetClFPat(CMClass,2); {Fill pattern} SetClFillFore(CMClass,cRed,cGrn,cBlu); {Fill fore color} SetClFillBack(CMClass,cRed,cGrn,cBlu); {Fill back color} SetClUseGraphic(CMClass,TRUE); {Use gfx attri at creation} SetClLW(CMClass,180mm); {Line weight} END; This section sets the attributes of the class based on the RGB values you specified earlier in the script. But it does not tell the object you are drawing to use the class attributes. But the next line switches the active class so that the class you set the attributes for is not active. So this code is not really doing much for you. I don't know exactly what you are trying to accomplish, but if you want to use the class attributes, you need to change the first block to make all the attributes ByClass instead of the settings that are shown. Then when you change the class the object will use the class settings. And if you do this you can simplify the script to remove all of the RGB setting code as that will all be done in the class setup. If you want to manually set the attributes as you are doing that is fine, but you can't manually set the attributes and then also expect them to use the class settings. It is one or the other. If you are using attributes by class you probably don't want to change the class attributes in the script that is drawing the objects as everything else in the file using those class attributes will also change. You will probably need to have a wood class and an aluminum class and set the object in the correct one rather than setting the attributes manually.
  8. Pat Stanford

    Script issue

    If you can share the script someone will be glad to look at it. I will when I can, but I am leaving on a trip later today.
  9. Pat Stanford

    Script issue

    The FillBack, FillFore, etc. are setting the defaults for the document. Any new object drawn will use those attributes. It sounds like you actually want to set all of the attributes to be ByClass so that when you change the class of the object the attributes will change also. Check out the SetLSByClass (and all of the other ByClass functions) to set the attributes by class. If you use the offline function reference, you have the option to "View By Class" at the upper left. Then check out the section title Object Attributes to see all of the functions that can be used to set object attributes. The off-line function reference is in the VW application folder VWHelp:Script Reference:ScriptFunctionReference.html
  10. Pat Stanford

    Vectorworks Fundamentals - Dimension error

    I sounds like you want to make sure you have the Allow Numeric Keypad Entry for Instant Data Bar Activation option in the second set of options. I you don't have this selected, then by default the numeric keypad is used to switch between the standard views. 2/4/6/8/5 Front/Left/Right/Back/Top. 1/3/7/9 Iso views. 0 Top/Plan.
  11. Pat Stanford

    Script issue

    For an object that already exists you need to get a handle to the object and use SetClass or SetClassN.
  12. Pat Stanford

    Vectorworks Fundamentals - Dimension error

    You probably want the first set to be either Use Floating Data Bar or only when tab key is pressed. Also make sure that one of the top two options in the second set is selected.
  13. Pat Stanford

    Controlling visibility using data visualisation

    The black holes appear to be a 2018 issue. They do not show in 2020. You should be able to just Update the viewport and not have to go between render modes. Or maybe since Wireframe is not a render more you do or you won't get the update button. Maybe use Hidden Line instead of wireframe? Good luck.
  14. Pat Stanford

    Controlling visibility using data visualisation

    I have it working here in both 2020 and 2018. Visualization in 2020 has been greatly enhanced, so if you really need to do this, you should at least consider upgrading. There is a very limited set of dates, so only a few dates will show a difference. I know everything will be visible in 1955, nothing will be visible before 1900 or after 2000, and at least some items will be invisible in 1991. You are correct. If you need multiple dates we can either modify the script to give you boolean fields for those dates or give you multiple scripts that store the data into different fields that can be used on different viewports. You are correct that the Enable should be on and the Record Field should be Year. For False the pen and fill should be None. I don't know why it is not working for you. Unless you are using OpenGL where it did not seen to hide objects properly. Year 1991 Year 1955
  15. Pat Stanford


    I am out of ideas. You should probably contact Vectorworks technical support directly. Sorry.


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.