Jump to content

Pat Stanford

Moderator
  • Content Count

    6,340
  • Joined

  • Last visited

Community Reputation

968 Spectacular

About Pat Stanford

  • Rank
    Vectorworks Veteran

Personal Information

  • Homepage
    vectortasks.com
  • Location
    El Segundo, CA, USA

Recent Profile Visitors

5,685 profile views
  1. How are you editing the TBB in your favorites? If you only edit in the local file there is not link back to the version in your favorites file. You either need to open the Favorites File in VW and edit the TBB there or you need to export the edited TBB Style to the Favorites File.
  2. Are you editing the Style or are you editing the Title Block Border (TBB). If you are using a Style then you need to be editing the style. These edits will update the local version of the style. If you want to put it into your library, then you will need to export it from the Resource Manager to your library file.
  3. Add on to my answer above. Another possibility is that some kind of dialog box has gotten opened and then sent the the background and hidden. Until the dialog box is closed you can't close the worksheet window.
  4. FActLayer gets the first object on the active layer. If you don't change the active layer to be design layer 1 then you are getting a handle to an object on a different layer and are then use ForEachObjectInList on the objects on a different layer. Try using FInLayer(Handle to design layer 1) instead of the FActLayer and you might have better results.
  5. @vassenYet again your objects are too far from the origin of the drawing. Move everything back to close to the 0,0 point of the drawing page. Also, your Wall Style is set to have no Fill. Edit the Wall Style. From the Definition pane click the Edit Wall Attributes button. Set the Fill to something other than none. The None Fill of the Wall Style is the biggest problem, but having the drawing far from the origin can cause this kind of problem also.
  6. I can't find a way to use the U or R values, but there is a Thermal Transmmittance available in the IFC data. ifcWallStandardCase:Pset_WallCommon:Thermal Trasmittance There are similar settings for curtain walls. HTH
  7. In a script the Layer Visibility should not matter. As long as you can get a handle to the object you should be able to work on it no matter where it is. If you are trying to manually select the object and then run the script on it the selection step will definitely be impacted by the Layer Visibility options.
  8. Not trying to minimize the brokenness that you all seem to see with this tool, but maybe a different perspective. In my (NSH) opinion, there are some things that are in VW because they check a box as being required by Marketing and they probably will never get any better. There are some things that VW knows the users are not happy with but either require substantial behind the scenes work to make happen, or are just too big of a project to deal with at this time. And then there are items like the Property Line tool. This is a tool that could work much better, but has not gotten enough complaints to rise to the top of the list of priorities. A long time ago someone wrote a description of what the tool was supposed to do and how it was supposed to work. It is possible that the person who wrote the specification didn't know what they were doing. Or it is possible that they were thinking of a different workflow to the way that you want to use the tool. In whichever case, the tool was coded and it meets the specification. When you say "Fix This", they look at the specification and say It is doing what the specification says, so it is WAD (working as designed). And it doesn't get any better. I would bet that most of the people at VW (Wes, Rubina, Robert, Erick, etc.) who have real world experience would all like to see the tool improved, but they are tasked with other projects. So if you want a tool that works, especially one that works with your workflow, you are probably going to have to help. And by that I mean, don't just point out the places where the current tool does not work, but rather start from scratch and write down exactly what what data you are going to start with, how you want to enter that data, and what do you want the end result to be. Give them multiple example data sets of the input so they can actually see examples. Yes, I know that is not your job. But a tool that is used once at the beginning of most projects is not going to see much love (compared to Windows or Walls, or Plants) as things that are used hundreds of times in every project unless you make it your job. Don't throw it on the programmers. They are very good at what they do, but they are given a specification and they write code to meet that specification. The programmers are not architects or VW users. They don't know what you know. Nor do they know what they don't know. If you write the specification, there is a chance that you will get an improved tool sooner. If not, it will get improved either when it breaks, or when someone else pushes for a tool that matches THEIR workflow. I can't promise that doing the above will get anything for you, but at least you will have done all you can. And then you can complain that you did all this work for them and they are still not responding. ;-)
  9. Post the script or direct message it to me and I will try to find some time to take a look. :-)
  10. It appears that there are three Spacing fields for Plant Objects. 'Plant'.'Row spacing' 'Plant'.'spacing' 'Plant Record'.'spacing' I don't know which one is used for which purpose. Probably best to set up a test worksheet and put all three options in and see which has the data you need. HTH
  11. No idea why it has not been added. Add a request to the Wish List forum.
  12. I am sorry if I offended you with my "good luck" comment. All I can say is that my (and apparently the majority of users) experience is very different than yours. VW would love to be able to track down and fix the crashing issues you are seeing. There are about 30,000 users on the forum. That is about 2% of the worldwide installed base of VW. There have been about 35 different users posting to this thread. A very small subset of a small subset. When you did your clean install, did you happen to bring forward a custom workspace? We have seen some people have issues with upgraded workspaces. Did you bring forward older template files? If so you might want to recreate those as well. If there is something corrupted in your template it could be giving you issues in all your files. Is there any consistency to a specific action that causes the crash? If not, it is possible that your machine may have a problem or bad memory. I am not trying to put down your experience and would like to try and help you figure it out. I am a user like you and I also run the Los Angeles users group, but other than that I have no relation with Vectorworks.
  13. LENGTH, WIDTH, HEIGHT in a worksheet are linked to the current view and the screen plane, so they don't work well for most objects. If there is a record in the PIO Parameters that contains the length you are looking for you can use a =Record.Field format to get the data you need. If these are just extrusions, you are probably out of luck. Unless you use a script to attach a Custom Record Format and store the length data there so the worksheet can access it. BUT then you need to remember to re-run the script to update the data when you make changes to the length of the extrusions or the data will be out of date. In a newer version of VW (2018 or newer I think) you can use a Worksheet Script so that the script will automatically run when the worksheet is recalculated. HTH
  14. Tamsin, if Fabrica is not buying for you I am!! You are always welcome!

 

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.

×
×
  • Create New...