Jump to content

Pat Stanford

Moderator
  • Posts

    12,530
  • Joined

  • Last visited

Everything posted by Pat Stanford

  1. 1. Don't store anything custom in the Library folders in the Application folder. These can and often are overwritten by updates. 2. If only one user needs the data store it in the User Folder. On Mac the path is USER:Library:Application Support:Vectorworks:2018:Libraries 3. If you want the office to be able to share you need to set up a Workgroup Folder in the VW Preferences. Search the Help and/or the forums for more information on Workgroup and User Folders.
  2. @Art V statement that all columns must be Record.Field is not quite true. It is completely possible to have columns with built in Worksheet Functions and columns with other formulas, but Record.Field of PIOs is the most common use of databases. Try the following. I recommend you try it in a test file or on a copy of your file in case you don't like the results. 1. Go to the Resource Browser and create a New Record Format named "MyRecord". In that record format create a field of type TEXT names "MyNote" 2. Attach the record to several objects in the drawing. 3. Create a new worksheet. Make a Database Row and set the Criteria to "MyRecord" is Present 4. In the database header row (i.e. 3, not 3.1, 3.2, etc) put in a formula of "='MyRecord'.'MyNote' 5. Type data into one of the database rows (3.2, 3,5 etc) in the MyNote column. 6. Right Click in the database Row Header and choose Select Item. 7. Goto the OIP and select the Data pane. You should see that MyRecord is attached and that the data you typed into the worksheet is now stored in the MyNote field. Once you figure out how the above works, you can change the record and field names as you wish. If you already have a record attached, you can just edit the record format to add the "MyNote" field. If you have a schedule of PIOs that is already based on the PIO record (i.e. Door or Window or ...) you can not edit that format. You will have to create a custom format and attach it to each instance of the PIO in the drawing. Or better, use one of the Custom Fields (at least in Doors and Windows) in place of MyNote so you don't have to manually attach the record. If you have an object in the schedule that does not have MyRecord attached, you will not be able to store any data you type into the worksheet. You MUST manually attach the record format to the objects to be able to store notes. If it is something that you have to manually attach a record to, consider making a "Blue" or "Red" symbol out of it so that when you place the symbol it reverts to the object with the record already attached.
  3. Three possibilities to get something similar, but no there is no way that I know of to attach a script to an existing object that will automatically run when the object is changed. 1. Write a script of Marionette and run it periodically to show objects that meet whatever criteria. 2. Create a worksheet that will list objects that exceed your 5 meter length criteria. You will have to manually recalculate to see the objects. You can then right click on the database row header and Select the objects from there. 3. Take a look at Viewport Data Visualization and see if you can use Records.Fields to identify what you want and do the coloring there.
  4. Any column in a worksheet where you want to the able to change data must be a Record.Field combination. It can be a PIO Parameter Record ='Door'.'User Field 9' or a user defined field "myRecord"."MyField'jt hou (apologies for any typos. I have been drinking for a long time.) But you can not enter data into a field that is not a Record.Field combination.
  5. Another possibility is that the palette got moved off the edge of the screen. Try resetting your monitor to a stupid small resolution (like 1024 x 768) with VW open. This will force all the palettes to move to the active screen area. Then set the resolution back to normal. The palettes should stay on the screen.
  6. My suggestion would be to edit your symbol definitions and attach a custom record so you can easily identify the screen parts from other symbols on the same layer. Then create a database row in a worksheet with criteria of Layer is "your layer name" and Record "your record name" is present. This will then give you a list of all of the screen parts in a single database. Add columns for the information you want to show. Probably Symbol Name. I would also add a column with a formula of "=count" If you then Summarize by Symbol name you will get a database that shows each screen part in a single row and the Count column will show the number of that part that are used.
  7. When you define a Workgroup folder, you only define the top level "container" folder. The paths INSIDE that folder determine what resources can be used from the Workgroup folder. To have things show up in the Favorites, you need to have nested folders inside the Workgroup folder of :Libraries:Favorites Inside of Favorites you need to put either the files you want to be favorites or an alias (shortcut) to that file. The files all need to be VWX files with the same version as your current Vectorworks. As Zoomer said, you can copy the entire (mostly) empty hierarchy from the User folder. If you want to add line styles, hatches, etc., and have them show up as default content, you have to put the file into the correct subfolder inside the Libraries:Defaults folder. Based on your first post, I think you want to define Z:\Library\CAD\Vectorworks\Vectorworks Workgroup Files as your Workgroup folder. Inside of that you need a Libraries folder, and inside that a Favorites Folder. That is where you want to place the shared favorites files.
  8. You have probably already looked at this but in VS, there are functions to change coordinates: ScreenVecToModelVec ScreenPtToModelPt2D ScreenPlanePtToPlanarPt PlanarPtTo3DModelPt Plus some others. I played with them MANY years ago, but don't really remember if I solved your problem or not. HTH
  9. Also, consider the versions. You are trying to open a AC2013 file with VW2011 released in 2010. It is not completely unexpected that VW2011 can't understand a file format that was not created until 3 years after it was released. You can ask the people who sent you the file to export it back to AC2010 or 2011 and you should be fine.
  10. I don't believe so. Project Sharing lets more than one person work on a single file at a time, but I don't think there is any way to edit the data in a file that is not open.
  11. No. There is not way that I know of to edit the date in a referenced viewport. You would have to open and edit the file from which the data is referenced.
  12. I posted my rule about time estimating a couple of weeks ago. Take the amount of time you think it will take and double it. Then use the next higher unit of measure. 5 min -> 10 Hours 10 Hours -> 20 day 20 days -> 40 weeks 40 Weeks -> 80 months 80 monts -> 160 years. 😉😉
  13. How much time should you spend automating something? Depends on how much time you save and how often you do it. https://xkcd.com/1205/
  14. Yes the images need to be Renderworks Textures saved in a VWX file. You can have as many textures in a single file as you want, or you can split and put each in a different file. Personally, I would probably put as many in a file as I could to make file management easier. So all the similar images for a show in one file and then possibly a separate file for the next show.
  15. Since Sam already wrote it you don't have to. I am certainly more proficient in Vectorscript than Marionette, but in My Not So Humble Opinion, Vectorscript will always beat Marionette when it comes to manipulating already existing objects. Especially if you are just working with attached data. I have not looked at Sam's script, but I am pretty certain I could do what you asked in less than 20 lines of code. Maybe less than 10. BUT depending on the number of lights you have, it might not be fast enough to run after every change. 10 lines of code x 1000 lights is still a lot to process.
  16. A script would be the easiest way, but least flexible. Would you want it to effect every light in the drawing/Layer/Class or only selected ones? A Worksheet could do this, but you would need to do a manual step to copy/paste the data from one column to the User Field column. But it would be more flexible in that you could decide which lights to do this for. And now we wait for @JBenghiat or @Sam Jones or one of the the Spotlight Gurus to tell us that it is easy if you just do these three steps. 😉 If you need help with the script or worksheets ask again.
  17. I have posted a couple of long posts about worksheets in the last month. Take a look and see if they help you. While not specifically about Plants, the ideas are the same. If they are not enough help, ask again.
  18. Start with the following thread and see if it gets you what you need. If not ask again.
  19. Recent article on upgrading the 2012 Mac Pro. Use at your own risk, but since the new MacPro won't be out until "Sometime" in 2019, it may be work considering. https://www.imore.com/how-upgrade-your-older-mac-pro-firmware
  20. @Mikedk64 You might already know this, but "Layer Scale" is a little bit of a misnomer. Yes, if you print from the design layer (at 100%), then that is the scale of the objects on the page, but when you use it while drawing it is actually more of a "Preset Zoom" factor. So with a design layer set to 1:100 as you draw a line, you see the actual dimensions in the Object Info Palette, in all the dialog boxes, and in the scale bars if you have them turned on. You don't have to do any calculations or adjustments, just draw while trusting the measurements that are displayed. When you take a 1:100 design layer and put it into a viewport at 1:100 on a sheet layer it will look identical on screen (and when you print it out). As Gerard said, things like Text, hatches, and line weights work much better when drawn at a scale "reasonably" close to the scale of the final output. No more having to put 700 point text on a design layer to hope it comes on on a 1:100 sheet as 6 mm tall. Try it and see. You might find you like it.
  21. @Julian Carr Sometimes having been around for a long time is a hinderance. I just found out about this one myself a few months ago. There is a new criteria called Visible Selection State. It only returns the objects that are individually visible (i.e. container objects) and ignores any selected objects inside those containers. Try count(((VSel=True))) In a file with a selected group made up of three selected objects, when I put the following formulas into a worksheet I get: Count(Sel=True) returns 4 Count(VSel=True) returns 1 I think this is what @WhoCanDo is actually looking for.
  22. It looks like to change the sort order you do have to change to None and then add in the new order you want. You can get to this by right clicking in the database header row. You don't have to click the little tiny disclosure triangle. But if you delete the first, at least they renumber while keeping the same order. How many sorts were you usually using before?
  23. Can someone post a file (without too many lights) and a copy of the generate paperwork worksheet for that file. If Kevin says it can't be done, I tend to believe him, but I would still like to look. I have a couple of tricks that might help. If you do convert to a database instead of a worksheet there needs to be a record.field combination for any manually entered data. If can be part of the standard PIO record or part of a custom record, but without a field, there is no way to type anything into a database.
  24. The only way I can think of to do this would be to create "BLUE" symbols of the different line types with the record attached. The Blue label is created when you check the Convert to Group option in the Create Symbol Dialog box. If you only have a single object (the line with the record attached), when you place the symbol it will actually insert it as a line and not as a group. Alternatively, a very simple tool could be created that would just attach the specific record to a clicked object.
  25. It has to do with how numbers are represented and the base units used in the drawing. Anything more than about 15 km (10 miles) from the origin results in a single pixel as being more than a base unit and you end up with some kind of an overflow condition and crazy renderings. Full details on on the board somewhere if you are interested, but for most of us, just knowing to stay near the origin is enough.
×
×
  • Create New...