Jump to content

C. Andrew Dunning

Member
  • Content Count

    788
  • Joined

Everything posted by C. Andrew Dunning

  1. At this point in time, as you've discovered, Video Screen doesn't understand overshooting. Truly sorry and now on The List...
  2. In the column header for drape count, try entering "=VALUE('Soft Goods'.'TtlDrpCnt')."
  3. For our present users interested in staying current and for anyone just looking for simple ways to improve productivity, we have just uploaded a few minor updates to our tools. In addition to the usual refinement here-and-there, 2 things you might notice: 1) We've been working with a few Audio ToolSet 2 users in adding a few fields useful for users working in the installation end of things. 2) For those of you who like the look of the graphics produced by the stock Callout tool but who want the convenience of that feature included within in your plug-in instances, SoftGoods 2 and all of the Audio ToolSet 2 tools now include text bubble options: Current users of our tools can use the usual links and passwords to get these updates. If you're not using our tools and want more info, visit: http://www.landrudesign.com/VWPlugIns.htm. Have a good one!
  4. Correct. There are 2 things going on, here: You can select a Class for one or more of the individual parts as you wish - using existing or new Classes. If you only want to assign a single part family, no problem. You can input any prefix you'd like and then automatically assign all parts to Classes, each Class having that prefix. The default "suffixes" are hard-coded. Again, you can change the names as you wish.
  5. Really? How so? Then, simply have the path follow the wall. That's how the EAPs work in all of our tools...
  6. Sounds a lot more difficult than it needs to be. Why not simply edit the Profile so that the Profile Insertion Point is on the face hanging on the wall?
  7. 2 instances in which the parts Classes are valuable: 1) For all of the "Landru-sourced" tools, by-Class attributes can be used to assign textures to the different parts - staging legs...drapery...speaker finishes, etc. 2) When assigned to embedded Classes, part visibilities can be controlled. For example, a user might want to see text labels or notes in one view/plate but not another. Just food-for-thought...
  8. Likely, the dimension data in the "__ATS-BumpModData" record attached to the Symbol you're trying to import is either in the incorrect format (must be a text field) and/or does not include units markers (like "mm"). Correcting one or both of those should get you going.
  9. I am trying to get my head around the "Truss Object" workflow as compared to the "truss Symbol" workflow - specifically, in terms of editing truss Systems/assemblies. In the attached file is a truss System/assembly created using the Truss Insertion tool and "Truss Object"-enabled Symbols. What is workflow YOU would follow (VW-ascribed or not) to...: 1) Swap out the 4 silver 10' sections for 4 black sections? 2) Swap out the right-end 10' section for an 8'? 3) Swap out the 4, 10's for 8, 5's? I've included other truss Symbols (enabled to work w. the Truss tool) for your convenience. Really simple under the "Symbol" workflow: Select a Symbol instance and, after clicking "Replace" in either the right-click menu or in the OIP, select the new Symbol - and then, if necessary, add needed sections. I'm not seeing the same simplicity w. the "Truss Object" workflow and would welcome any counsel. 2020_Truss_Tinkering.vwx
  10. Multiple answers: 1) Other than meeting the 4 criteria I posted, yes, that dialog is the only way to assign curtain/drapery color if using the "Opaque" setting. With that setting, the tool generates the fabric Texture and manipulates the color of the underlying geometry - which is used by the Texture. 2) You CAN...if you really want to...change the color by changing the settings of the Texture definition. Just don't change the name. If you do that, the tool will simply re-create and apply the stock Texture. 3) You can also change the color by choosing the "Custom" option and choosing a specific Texture that carries with it specific color (like the Rose Brand fabrics do). As to your last question, to my knowledge, the related calls in the language in which the softgoods tools are written do not allow for "By-Class" color. You raise good questions and I am investigating options. (BTW, I am not a VW engineer or employee. I am simply the developer of several of the Spotlight tools, including Soft Goods.)
  11. 4 things: 1) A given part (Curtains, Hardware, etc.) has to be assigned to a Class through the "Classes..."/"Parts Classes..." dialog. 2) The chosen Class has to be set to apply Textures at Creation. 3) The entire Soft Goods/SoftGoods 2 object must be set to "Class Texture" in the OIP Render tab. 4) The Fill Color for the entire object must be set to apply color by-Class. (The actual Fill Color for the over-all object is irrelevant. This simply functions as a toggle to enable by-Class coloring.) I know this seems pretty convoluted. We simply needed to "protect" the settings instated by the "3D Curtain Options..." dialog as much as-possible. The current tools do not have this feature.
  12. Josh and Kevin are correct...: "Curtain" does pre-date SoftGoods 2/Soft Goods. A "converter" routine was never created.
  13. An option: Add that Class to your Template and make it invisible in all of your preset Saved Views.
  14. Assume square tubing and extrude squares, rectangles, and polygons (from a side view - for the diagonal lacing).
  15. Grant - Use Stage Plug instead of Stage Deck. And, try either the "Border" or "Simple" structure.
  16. 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.
  17. 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.
  18. 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!
  19. 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)?
  20. 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!
  21. If you DM me your user name and e-mail address associated with your license I'll send you the new download info.
  22. Lec...no "war," perceived, at-all. Just adding to the conversation...
  23. 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...

 

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