Jump to content

C. Andrew Dunning

  • Content Count

  • Joined

Community Reputation

116 Spectacular

About C. Andrew Dunning

  • Rank
    500 Club

Personal Information

  • Occupation
    Lighting Designer
  • Homepage
  • Location
    Nashville, TN, USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Assume square tubing and extrude squares, rectangles, and polygons (from a side view - for the diagonal lacing).
  2. Grant - Use Stage Plug instead of Stage Deck. And, try either the "Border" or "Simple" structure.
  3. Really??? All of my tools have indenting and enabling controls in kObjOnWidgetPrep (event 41) and, other than the issues in a build or 2 of 2020, I've had no issues.
  4. For me, it has depended on the build. The issue has come and gone...and, I don't remember the build in which I first saw it.
  5. You are correct. The stock CreateMarkerPopup call doesn't, either. I had asked the question based on what I'd seen in the Developer Wiki. As things are, all is working well. Thanks!
  6. Thanks, Julian. What gets returned if "Class Thickness" is chosen (if that is even an option...w. CreateMarkerPopup the equivalent isn't in the list...at least, in the VS version)?
  7. Good morning! Might any of you be able to lend insight into getting data out of a pop-up created using "CreateLineWeightPopup?" I did find "GetLineWeightChoice" but I'm not sure if that applies as "Class Thickness" is one of the options and that call simply retrieves the line weight in mils. Thanks!
  8. If you DM me your user name and e-mail address associated with your license I'll send you the new download info.
  9. Lec...no "war," perceived, at-all. Just adding to the conversation...
  10. Interesting to see the direction this thread headed... A few comments regarding the "3rd-Party" part of the conversation: 1) I well understand Lec's concern about an apprarent need (to him) that is not being met by the stock VW packages. I've been there so many times that I've lost count. 2) Sam is quite right about the breadth of disciplines VW covers. VW leadership has to make daily decisions about where to apply resources and about which features (or, approaches to implenenting features) fit or don't fit defined conventions. Along w. that, it CAN be quite frsutrating to see another industry getting love when one's own is seemingly getting ignored. The evidence is that, using Spotlight as an example, users from that area aren't really "poorer stepchildren" when one considers all of the specific effort that has been applied, there, recently. The catch is that, within the microcosm of Spotlight, the decisions I just mentioned have to be taken... 3) Echoing Sam, this is where the beauty of having 3 different options for developing proprietary or 3rd-Party solutions lies: · Very focused or customised commands and tools can be created. · Potential needs can be explored in a way that could be difficult under the corporate umbrella. · Likewise, other approaches/conventions can be explored in a way that could be challenging under the corporate umbrella. · Intimate interraction with developers is more possible for more users. · Many developers are creating solutions that they need in their own day-to-day "other" jobs - using approaches and conventions that "think" like they do...that fill sometimes difficult-to-articulate needs...approaches and needs that can be incredibly hard to understand if one is not really immersed in a given discipline. · Faster turn-around on enhancements and fixes is often possible. · Commands and tools are seldom tied to a specific VW package. 4) While this might sound self-serving for me to say, I'm with Sam in being quite surprised at the hesitation of a lot of users to take advantage of 3rd-Party commands and tools - some at little to no cost. Yes, there is risk involved. Is there any actual support? Will the command or tool be available in a month? Does the command or tool follow official conventions? I've found so much value in 3rd-Party offerings that those risks are more than acceptable. And, the more I invest in other developers, the more incentive they have to continue their work...
  11. Steve - That error message means the tool is being asked to place a projector in a way that is impossible - such as a vertical offset that is more than 90°. Try a smaller vertical shift amount or a different lens spec. and see if the issue gets corrected.
  12. We are happy to announce Vectorworks 2020® versions of our tools have been released! In addition to getting things ready for Vectorworks 2020®, we've been working on the usual "under-the-hood" refinement and on adding some features several users have been requesting. As evidenced by the Audio ToolSet tools' "Symbol" functionality released earlier this year, we really do listen to your requests! The most apparent improvements you'll see have to do with text display in the VideoScreen 4 tools. You'll see things like the ability to generate 3D text blocks (discussed in one of the Facebook VW groups recently)...customize item labels...and, to display additional textual information. If you're one of our users and purchased one of the VideoScreen 4 licenses or a Producer's Pack 3 license since February 11, 2018, these updates are available to you free-of-charge. If your license is older than that, we believe that you'll find our upgrade offers to continue to be quite generous. If you hold a license to one of the other tools, your current link and password will allow you to download a version for Vectorworks 2020®. If you're not one of our users, yet, and would like more info, visit one of the links in my sig for more details, to download manuals, or to check out the upgrade offers. Happy Vectorworking!
  13. No. Not a stand-alone tool. Simply treated as another "Department" in our RigPoint tool.


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...