Jump to content

Pat Stanford

  • Content Count

  • Joined

  • Last visited

Everything posted by Pat Stanford

  1. Pat Stanford

    Realistic hardware spec for OS X

    I agree with Josh, but if you look at the benchmark scores, the 2018 is substantially faster. 2018 2.6 i7 vs 2017 2.8 i7 is 16% faters in single core and 46% faster in multicore operations. If you are only doing 2D drawings and models, the 2017 is probably fine. If you are going to be rendering then the 46% difference is probably worth considering as it can save you a lot of time. The adage is always buy the most you can afford. Spending a little more now and not having to replace the machine for an extra year is probably worth it. Checkout the Apple Refurbished page. Apple.com scroll all the way to the bottom of the page. I think it is in the second column of links.
  2. Pat Stanford

    Why do my doors keep jumping out of the wall?

    Alternatively, make sure the mouse pointer is within the wall when you drag it. If the pointer is over the wall it will insert/remain inserted. If the mouse pointer is outside of the wall it will end up as a door or window instead of a door or window In Wall. Especially easy to do if you grad the door swing instead of the frame.
  3. Pat Stanford

    Truss Counting

    Working from memory here. Edit the database criteria and make sure the check box for Include components of PlugIn Objects is selected. You might also the the Symbol and Group check boxes also. I'm not sure how hanging positions handle the truss, but this will probably get you what you want.
  4. Pat Stanford

    Archiving VW files

    The problem with VW (and actually most software) is the that hardware and operating systems keep changing. That means that at some point you end up with a condition where even if you have an old version of the software, it will be incompatible with the current OS and hardware. So when you are archiving you should actually archive not only the files, but also the original program, and probably even the original hardware. I have been considering, but have not yet implemented, an idea of doing a "virtual" archive of the hardware. By that I mean setting up a virtual machine with the current OS and current version of VW and keeping that as the backup. Then when you need to access the backup you are not rummaging through junk stores looking for old hardware, but only needing a way to run the old virtual machine on current hardware. Something that I would expect to be much easier. At one time I actually set up a double virtual machine running on an Intel Mac. In the first virtual machine I ran a version of PowerPC OS10. Then inside of that I ran a copy of SheepShearer which is a virtual machine running 680X0 code. This let me run OS6 or 7 and Minicad 5 on a current Mac to rescue some old files. The question about archiving is always how much of the data do you really need to get back. Batch convert occasionally is an OK idea, but unless you have the time to rework all of the drawings to make sure they converted correctly, you are still likely to lose some information. Especially after the 2nd or 3rd conversion. What percentage of the files do you really think you will ever need the geometry from again? If it is a high enough percentage, then it might be worth the time to do the batch convert. If it is a low percentage, it might be better to just figure out how to recover the files you need when you need them. It all depends on what the value is and how much time it would take to recreate (since you already know what to draw, the recreation, if needed, will probably take far less time that the original design. At the very least I would make PDF copies of everything. Probably even PDF/A which are designed to be archives and be recoverable at any time in the future. That way you can at least see what the output of the drawing was even if you can't access the geometry. Difficult question with no good answers. Kind of like preparing for earthquakes. You do what you think needs to be done and then cross your fingers and hope that you don't ever need it, and that if you do that it is enough. Glad to talk about this more if you have questions. Oh, yeah, and remember, it is not backed up unless it is stored on at least three different types of media in at least two geographically separate locations. Yes, I know the Amazon cloud promises 99.9999% recoverability, but what happens when you are the 0.0001%??
  5. Pat Stanford

    Is it possible to select multiple extrudes by height?

    Unfortunately, @markdd is correct, you can't select multiple objects from a summarized database row in a worksheet. Would be a nice wish list request. The following script will select all extrudes in a drawing that have the same extrude length as the first selected object on the active layer. It uses the extrude length, so even if they have been rotated or moved it will still select them. If you actually need a script to only select extrudes with the same "top" Z position, that will take a little more work. Procedure SelectSameHeightExtrude; {If the first selected object in the drawing is an extude} {this script gets the height of that extrude and selects all} {other extrudes in the drawing that have the same height.} {January 4, 2019} {© 2019, Coviana, Inc - Pat Stanford pat@coviana.com} {Licensed under the GNU Lesser General Public License} {Based on SelectSameLengthLines} {February 13, 2012} {© 2012, Coviana, Inc - Pat Stanford pat@coviana.com} {Licensed under the GNU Lesser General Public License} Var H1 :Handle; OLength :Real; Procedure DoIt(H2:Handle); Begin If HLength(H2)=OLength then SetSelect(H2); End; Begin If GetType(FSActLayer)=24 then Begin OLength:=HLength(FSActLayer); ForEachObject(DoIt,((T=XTRD))); End Else AlrtDialog('First Selected Object Must Be An Extrude.'); End; Run(SelectSameHeightExtrude); Select EVERYTHING in the code box above and paste into a new blank Vectorscript edit window. Test first on a backup copy or sample file. Very minimally tested, but since all it does is select damage is unlikely. Now warranty expressed or implied. User must determine suitability for their requirement. 😉
  6. Pat Stanford

    Hoist Symbol/ Plug-in Object

    @Sam Jones Can you comment on this please?
  7. Pat Stanford

    Worksheets - window schedules

    You only need to change the formula in the database header row. Unless you need to edit the criteria to change the windows that are shown in the database, you don't need to change the criteria. The criteria only effects the objects that are shown in the database. Column formulas can refer to anything about the object shown. If you specify a Record.Field that does note exist for an object you will just get a blank. There is definitely something weird with Userfld2. I tried it and it would not take anything. I then went to the OIP/Settings for the window and edited the User Field 2 there and it showed up in the worksheet. After that I was able to edit from the worksheet. ??? If I can replicate in a new file I will submit as a bug, but for now, try and edit one windows from the OIP and see if that will force the formula to work correctly.
  8. Pat Stanford

    Worksheets - window schedules

    All data in a database section of a worksheet has to be an attribute of the object (Layer, class, name, type, etc.), information about the object (XCenter, YCenter, etc.) or a Record.Field. The Record.Field can either be from the PlugIn Object Record or from a manually attached custom record. There is no way to just type things into a database cell in a worksheet. That being said, if you have a record.field that is formatted as text, you can set that to be the cell value and through the magic of 2-way worksheets, any changes you make in the worksheet will be stored with the object and be accessible from the OIP. For windows you can use the User Fields if you are not already using them for something else ='Window'.'UserFld1' Change the 1 to whatever (1 to 10) user field you want to use. If you are already using the User Fields, you will probably need to add a custom record and use those fields.
  9. Pat Stanford

    How to report dimensions of symbols or objects in a worksheet

    In VW2019, the worksheet returns the correct width/height/length for extrudes regardless of their rotation and location inside of outside of symbols In VW2015, the worksheet returns the width/height/length for the object bounding box, not the OIP values for the extrude for objects that are not in symbols. For objects that are in symbols, it will return the values based on how the object is drawn inside the symbol definition. Even if the symbol instance is rotated, it will still give you the "orthogonal" values from in the symbol definition. So, you will have to access the extrusions inside the symbol definitions instead of the symbol itself. The following Database Criteria will give the values of all extrusions. You will need to add some other criteria (probably a class would be best) for the extrusions inside the symbols to be able to limit the table to just the objects in the symbols. And if you do it this way, you will not be able to access the symbol names since the criteria is based on the extrudes and not the symbols. If you instead Name the extrudes in the data pane of the OIP, you can access that name with a formula of =N. Let me know if you have more questions.
  10. Pat Stanford

    How to report dimensions of symbols or objects in a worksheet

    Can you post a simple test file with a few of your symbols and a worksheet that is not giving the correct information? You may need to attach a record and use that to store the values and then use the stored values in the worksheet. A fairly simple script could be used to store the values.
  11. Can you ask the person who gave you the file to export it back to VW12?
  12. Then either it is corrupted or it is not a VW10 file. Could it be a VW 2010 file? That would be newer than the VW12 version you have and could be the reason it will not open. If that is the case you will need to find someone with VW2010 to open the file and Export it back to a VW12.5 format. The best option would be for someone with an actual version of VW2010. If you do a newer version it will first have to convert to the new version and then export back. More likely to lose data that way.
  13. It should just open. VW 12.5 is capable of opening and converting files back to at least Minicad 7. Put the file on your laptop. Open VW 12.5. Go to the File menu and choose Open. Navigate to the file. Click OK.
  14. Pat Stanford

    Hoist Symbol/ Plug-in Object

    Sorry for the delayed response. Red Symbols are automatically converted to a PlugIn Object upon insertion. I think that is a problem when used with the Hoist object. If you don't want this setting, select the Symbol in the Resource Browser, right click and choose Symbol Insertion Options and uncheck the Convert to PlugIn check box. Search the VW help for 'Symbol Types' for more information on the different types of symbols.
  15. Did you ever get this figured out? The 92903 number is about right for conversion of mm2 to ft2. Check the Area Units in the Document Preferences.
  16. Pat Stanford

    Snapping to Greyed Objects

    My mistake. The 'Y' key toggles the Smart Cues. Those text boxes that tell you what kind of point you are snapping to. The '`' (back tick) key disables snapping while it is held down. Since the snapping is working outside of Edit mode, I don't have any more good ideas. It sounds like you have restarted VW already. If you don't get any other suggestions, my next idea would be to quit VW, drag your User Folder to the desktop and restart VW. This will create a new user folder, but you will have to reset your preferences to your liking. If this does not fix the snapping issue, trash the new user folder and drag the original one back.
  17. Pat Stanford

    Snapping to Greyed Objects

    Are things snapping when you are not in Edit mode? The 'Y' key toggles snapping on and off in the default workspaces. Could you have accidentally hit that and suspended snapping?
  18. Pat Stanford

    How to report dimensions of symbols or objects in a worksheet

    As long as you are using Extrudes, you can use a formula of =Length, =Width, =Height to get the dimensions of the bounding box of the extrude. As long as you are using rectangular extrudes you should be OK. If you put the Extrudes inside of Symbols, you will need to edit the worksheet Criteria and check the Include components of Symbols check box.
  19. Pat Stanford

    Window Schedule Worksheets

    Yep. Remember that all items with the same criteria type are OR'd together. So your screen shot says give me all of the windows whose OnSchedule OR IDPrefix is 'W1-' If you really need to be this complicated, you can manually edit the criteria in the data bar, but you will lose the ability to edit using the criteria builder. After you edit the criteria and click OK to the criteria builder dialog box, take a look at the data bar. When I do that with a slightly simpler set of criteria (only one layer), I get Notice the vertical bar character between the IDPrefix and OnSchedule sections of the criteria. That specifies the logical OR function. That means the criteria will return every window on Design Layer-1 which has the OnSchedule checked OR has a prefix of 'W1-'. Click in the data bar and edit the formula to replace the vertical bar with a '&' ampersand and you will now only get windows that are BOTH On Schedule AND have a prefix of 'W1-'. It used to be that if you tried to edit a criteria that had been manually edited you would get a warning that you could not use the criteria builder. In VW2019, it appears that the criteria builder will open an just overwrite any manual changes you have made, so be careful.
  20. Pat Stanford

    Window Schedule Worksheets

    If it is showing more than you expect, then you did not get the criteria correct. When you say set the criteria you mean you are right clicking on the database header row and choosing Edit Criteria? What are the criteria you are setting? Layer is "your layer" Field Value "ID Prefix" is "W1-" Since the option is for the field value EQUAL to what you type in, make sure you include the dash. Can you screen shot your criteria and post it for us to take a look at?
  21. Pat Stanford

    Snapping to Greyed Objects

    Are your Layer Option and Class Options set to Show/Snap Other, Snap Others, or Grey/Snap others?
  22. Pat Stanford

    Organizing the Hoist Worksheet

    Most likely the Header Row is hidden. Check the Worksheet menu:View and make sure there is a check mark next to Database Headers. If not select it to turn on the header view.
  23. Pat Stanford

    Saving File Templates to Server

    Take a look at the threads I referenced in this post: Set up a Workgroup folder that everyone can access and store the files in the correct folder and everything should "just work"/
  24. Pat Stanford

    Creating a Workgroup

    Take a read through these two threads and then come and ask again if something is not clear. The second thread includes links to this post: and this thread:
  25. Pat Stanford

    Viewport Class Overrides- not working??

    To get it to work properly within symbols (and other container objects, i.e. groups and PIOs), each of the contained objects also needs to have the attributes set to ByClass. And just for the sake of saying it again, in order for contained objects to be visible, the containing object must be visible also. So if you create a symbol and put the symbol instance into Class A and then make Class A invisible, every object inside the symbol will be invisible also, regardless of the visibility settings of their individual classes.


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.