• Content count

  • Joined

  • Last visited

Community Reputation

65 Excellent


About ericjhberg

  • Rank

Personal Information

  • Occupation
    Landscape Architect
  • Homepage

Recent Profile Visitors

950 profile views
  1. Right click on delete on leader attempting to delete.
  2. In VW2018 we have been having issues with our custom workspaces resetting upon each open. A few of us prefer to stack our Basic and Landmark toolbars on the left side of the screen, 2 tool columns wide each. Upon open in 2018, these tool sets completely collapse every time, no matter how the workspace is saved. Only been an issue in 2018, never before.
  3. @markdd This is exactly what I am hoping to do also. Based on Pat's answer above, it may not be possible though? Curious if you've learned anything new on this? Thanks.
  4. I am wondering if there is a way to use a script to populate a worksheet with all of the Plant Plug-in objects that are located within a file's Resource Manager, but not necessarily placed in the drawing. Could this also be refined to populate the list with Plug-in Objects placed within a specific folder in the resource manager? Can the script mine the data of the plug-in object to list the latin name, common name, schedule size, etc. similar to a database worksheet does for objects placed in the drawing. Thanks.
  5. Thanks @Christiaan. Regarding all-in-one files, that is similar to our testing and what has forced us in to the referenced file workflow. We have a few of those very large projects you speak of and we haven't been brave enough to put them into one file. I don't think the question is whether or not the tool should be released. My biggest problem with this tool, and several others for that matter, is that there is no support or documentation that would help the user figure out that it doesn't work in a particular workflow type. It's as simple as releasing some basic documentation that would state, Edit Section In-Place does not work through viewport references. Instead, you are forced to figure that out on your own, and too often waste the time finding out that it won't work. Also, your assumption is that it will someday work with WGRing. There hasn't been a lot of support or tools that have been developed to support WGRing workflows to date, and I doubt the engineers are spending time trying to figure this out. This workflow based discussion is pretty basic. It's the starting point for the practical use of the software. The first question I have to answer when building a project is All-in-one or WGReference, and if I choose WGReference, there is no support to tell me...wait a second, that means you can't to this, that, this, that... Honestly, much of the time I wonder how in touch VW is with their users and how they actually use the software. The much bigger question to me here is workflow. It is pretty obvious that VW sees the future in the all-in-one approach, and for most projects, most users, that approach probably works fine. We may be on the outside of this discussion in having projects that are so large that (referring back to the original post) they contain hundreds of design layers and sheet layers and the file sizes quickly explode. It is my hope that VW tries to become more competitive in this large project arena and try to mitigate these circumstances.
  6. Emphasis on the "should". In previous versions this was definitely the case, but if you are using VW2018, beware that there is a bug that affects how symbols appear in worksheets using the =IMAGE function. I have been told that a fix to this bug is expected in SP3 which should be forthcoming soon I think, but just worth noting.
  7. Our team is having trouble with .dwg imports that contain clipped xrefs and clipped blocks. Objects outside of the clipped area are being imported into vectorworks as live linework, and contain schedules, exploded views, etc. We would like to be able to import these files with the clipped objects excluded or cropped. Is there a way to accomplish this? We have tried using the "Ignore Block Clipping" tool, but this doesn't change or alter the import at all?
  8. We have been doing the referenced sheet layer file approach for awhile but haven't ventured into project sharing yet...mainly for the two reasons mentioned in the original post. @ChristiaanHave you found your new all-in-one approach to be better/faster than the old referenced technique? I ask because although I could imagine all-in-one file sizes to be much larger, they may in fact be faster and easier to use because of the seeming cumbersomeness of references. I also find it amazing that these workflows are not fully considered when developing tools like Edit Section In-Place. For one feature of the program to completely drive how you use it is frustrating. Plus, the only way to find this pitfall or "straw that broke the camels back" is to completely go down the road and then realize the lack of functionality...then have to reverse course and rebuild. Unfortunately Edit Section In-Place is only one of these issues we uncover. There are many more that affect best workflow practices that I hope VW can consider. They include, but aren't limited to, VW2018 Titleblock Styles - Still unsure how these are truly used in a referenced file project workflow Detail-Callout Markers - Forces detail viewports to be in the same file as the plans/model Worksheets - Many incapable of determining information when attempting to pull through Viewport References. This forces the worksheet to appear in the design layer/model file and be referenced into the sheet file. We have been struggling with this issue for a long time and I still haven't ever gotten a straight answer of how the one-file approach is supposed to work in regards to extremely large files and potentially hundreds of sheet layers and design layers. Hoping to get a better answer someday.
  9. This is a great request and I know has appeared on here several times before...hopefully repeated exposure will push the development of site model!
  10. That's awesome!!! It works beautifully and in seconds. Thanks @Pat Stanfordfor saving us hours of manual time!
  11. I have also had this happen, undo skips multiple steps. I've never been able to validate how far in the undo history it has gone, but I always immediately check my undo preferences and they haven't changed?
  12. @Alan Woodwell. Wow! The marionette script is an impressive tool. I could definitely see using that for random placements. This isn't actually what I was asking though. I am looking for a way to essentially do the following steps, but for over 500 plants, defined as favorites in the Vectorworks Plants plant database. Create Plant (Ideally from a really basic circle) Get Plant Data (opens Vectorworks Plants plant database) In the database, select a unique recrod marked as a favorite Run the command Vectorworks > Use Currently Selected Plant Record to update the Schedule information of the Plant Definition Copy the Latin Name Field and apply/paste it into the Plant Symbol Name field Update/Input the Insertion Options, Spread, Height, and Spacing fields with information present in the similarly named fields of Vectorworks Plants plant database record Repeat...again for every plant record marked as a favorite in the Vectorworks Plants plant database Thanks again for your help. Much appreciated.
  13. Hmm, I don't think it worked. I'm not that familiar with scripts. The desired RGB file is 65535, 65535, 65535 I've attached the file in question. You'll notice that I've manually adjusted the first few to the desired Magenta color, but when I run the script, it doesn't appear to work? Thanks again! _PCLD Generic Plants.vwx
  14. No, not by class, just another color. Nope, no other symbols. This is a library file I am just trying to clean up. Thanks for the quick reply!