Jump to content

C. Andrew Dunning

Member
  • Posts

    1,042
  • Joined

Posts posted by C. Andrew Dunning

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

    BubbleDemo.jpg

    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!

    • Like 3
  2. 4 hours ago, Smatticus said:

    If I understand correctly, the Soft Goods object sub-classes do default to the overall object class (<Soft Goods Class>)?

     

    Correct.

     

    4 hours ago, Smatticus said:

     This drop-down is what I was particularly confused by, especially juxtaposed underneath the default prefix "SoftGoods." An object and it's default class prefix having the same name makes sense but it is also a source of confusion. I think <Soft Goods Object Class> or just <Object Class> would be more clear. The "Use Standard Classes" button I also found confusing until I tested it. The help description says "...to the predefined default classes using the specified prefix..." What predefined defaults? Predefined in settings somewhere?

     

    There are 2 things going on, here:

    1. 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.
    2. 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.
  3. 18 hours ago, Kevin Allen said:

     

    Exactly. If adding a crown to a box set, I trace in the plan view with the Polyline tool. Offset that line by 50% of the thickness of the moulding. Fiddle to get position and extrude. Fiddle and then Trim. For a portal. I trace the opening in Front View, Offset and place the profile  in the Plan View, Extrude.

     

    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?

    • Like 3
  4. 13 minutes ago, Smatticus said:

    ...sub part classes for objects...making the actual class assignment of the object as a whole somewhat meaningless in certain situations and respects.

     

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

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

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

    • Like 3
  7. 1 hour ago, Smatticus said:

     

    This does seem somewhat convoluted and I am a bit confused. Is the "3D Curtain Options" the only way to assign a fill color to the curtain (viewable in 3D)? Which cannot be altered through any referenced means (class, texture, etc)? If I want to use a reference for the curtain's color in 3D is it REQUIRED to be a texture rather than a fill color? The thing I don't understand about "3D Curtain Options" is why there isn't just an option, under "Opaque" for example, to get the desired color from a class... the way most other appearance attributes work in VW.

     

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

  8. 7 hours ago, Smatticus said:

    1) How do I get the soft goods object to take its color from its assigned class?

     

    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.

     

    7 hours ago, Smatticus said:

    2) One thing I liked about the old curtain object was when a traveler curtain is open it shows the curtain material stacked up with a tighter pleat spacing. I like this because it emphasizes visually that the curtain is open in 2D/plan. Is there an option I'm missing to create this behavior?

     

    The current tools do not have this feature.

    • Like 1
  9. 2 hours ago, Julian Carr said:

    I'm not seeing any issues either, but it might depend on where in the code you are calling it. Should be in kObjOnInitXProperties (event 5).

     

    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.

     

  10. 27 minutes ago, Julian Carr said:

    CreateLineWeightPopup() doesn't give the option to use class thickness Andy. 

     

    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!

  11. 24 minutes ago, Julian Carr said:

    Try GetLineWeightChoice() Andy. At least that's what I use.

     

    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)?

     

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

  13. 2 minutes ago, scottmoore said:

    you are now discussing the functionality of this potential product, one on one, with the actual developer. It doesn’t get much better than that in the software development world. 

     

    !!!!!!!!!!!!!!

    • Like 1
  14. 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...

    • Like 1
×
×
  • Create New...