Jump to content

C. Andrew Dunning

Member
  • Posts

    1,151
  • Joined

Posts posted by C. Andrew Dunning

  1. 39 minutes ago, Tom W. said:

    Can't you just use a uniform '#' for all of the placeholder texts? Then the rectangle will expand to the width of the longest text in the instance of the tag. Or maybe I misunderstood the issue.

     

    Yes and No...

     

    The default field contents and the dialog label are one-in-the-same.  So..."#" wouldn't be appropriate.  -BUT-  Changing the defaults/labels to shorter strings works beautifully.  So..."Name," "Dept.," and "Change" work.

     

    So...the box WILL change dynamically as-desired but its starting-point reference is a function of the DEFAULT string length AND the Dynamic.

     

    So...good call!

     

  2. 11 minutes ago, Nikolay Zhelyazkov said:

    There is currently no way to tell that you want only the longest text to be with fixed distance, because you can only set that you want fixed distance between a text and the boundary. You can achieve what you want if you constrain only the widest text to the right but the problem is that you do not know which is the widest text as its content is dynamic and changes with each data tag.

     

    1)  This is not what has been said in the past.  Other engineers have affirmed that what I am wanting to do is possible - as shown in the other D.T. in the file I posted.  The solution in that D.T. is what was suggested by another engineer.

     

    2)  Even when I pick one of the 5 fields to use as a single reference - 1 that I assume will be the longest - things still do not work correctly.  I tried that before submitting my initial question.  I am 100% open to your showing me that working w. a single-field reference...

  3. 1 minute ago, Nikolay Zhelyazkov said:

    @C. Andrew Dunning Here is an image showing how the fixed distance constraint is working as designed.

     

    image.png

     

    I don't think you are understanding what I'm saying.

     

    Yes; the fixed distance constraint IS working - relative to "Department."  The desired margin IS 1/8".

     

    BUT,  Department (and, the other fields) is stretching incorrectly.

  4. 24 minutes ago, Nikolay Zhelyazkov said:

    Let me know if you still think that this is not working as expected.

     

    No; it isn't.

     

    Using the image you referenced, Date is the longest.  In-theory, the other fields should stretch to match it and the margin should be relative to that stretched width.  Instead, "Department" is stretched far beyond what it should be and the margin references that field.  - OR -  As Date is the longest, the margin should reference that field and the other fields should stretch to fit the margin.

     

    Again...the desired outcome is that the right side of the box is constrained to a given distance from the widest field - which could be any of the 5.

     

    34 minutes ago, Nikolay Zhelyazkov said:

    image.png

     

    Look again at the graphic you posted.   Date is the widest, but the other 4 fields are stretching beyond its width - for Time, a little and for Department quite a bit - and the margin is referencing the resulting widest field, which is Department.  So...the margin might be behaving correctly but the stretching of the 5 fields is not.

     

     

  5. I believe there might be a bug related to the text block re-sizing.  I understand how the alignments are supposed to work but the tool is adding unnecessary spaces.  See the instance in the attached file with only "-" in the 3 User-Entered Fields.  Compare with the PIO Data-associated fields in the Seating Section label D.T.

     

    Change Data Tag - 2.vwx

  6. I have a D.T. w. a rectangle bounding box that I want to re-size with data edits (to track a margin w. the longest of 5 fields).  So far, in trying different settings, I either get no margins or text fields that expand in  unwanted ways.  I have a similar D.T. (but, w. only 2 fields) that works as-expected with the same settings.

     

    Anyone give me a hint as to what I've missed...?

     

    Change Data Tag.vwx

  7. 8 hours ago, symo said:

    Thank you @C. Andrew Dunning

     

    Yes, thats right

     

    Food-for-thought if you want the Class structure saved in your Template:  Place an instance of the PIO in-question, change the defaults to suit your wants and get the Class structure in the Parts Classes dialog set the way you want it.  Click "OK" an let the PIO generate the Classes.  Delete the PIO instance.  Re-save your Template.  The PIO settings will be saved in a hidden Record and the Classes will be added to your Template structure.

     

    • Like 4
  8. 6 hours ago, symo said:

    where in VW can I pre-assign these classes before I insert any symbols into my drawing?

     

    Echoing Kevin...

     

    In the "Parts Classes..." dialog, you have 2 options:  1)  You can set each part Class individually using the pop-up menus - or - 2) You can click the "Assign Default Classes with Prefix," which will set up a default Class structure for you.

     

  9. 40 minutes ago, livespace josha said:

    - In the "Text Options" window, there is an option to assign a projector a unique ID. This is super helpful for big setup. ...but I can't seem to find this value in the OIP and I can't pull it into a worksheet. Any workarounds?

     

    2 answers:

    1. If you use the Landru Design version of the tool, you'll have "Position" and "Unit" fields visible in the OIP for each projector.
    2. While not visible in the OIP, projector ID data is stored in 2 hidden fields: "__ProjIDText" and "
      __Proj2IDText," which can each be displayed in WorkSheets.

     

    • Like 1
  10. 2 things:

    1. The line assigned to the "NonPlot-Loci" Class is hard-coded so you can't delete it.
    2. The reason the line is so long and the bumper isn't appearing correctly (and, that the speaker isn't drawn correctly) is that the data in the Record attached to the Symbols is not correct.  The different dimension fields all must be "Text" fields and must include the correct units marker (like "mm").  Likely, the fields in the Records attached to your symbols contain metric values but VW is treating them as imperial.

     

  11. 2 hours ago, Sam Churzin said:

    Hello everyone! I've faced with strange a Speaker Array tool behavior. My subs and top are not at a zero point more other tops overlap each other. What is the reason of that? I've checked all my 3D geometry positioning in speaker symbols and frame symbol. Everything is at zero point. Any suggestions?

     

    Like @klinzey said, there is likely incorrect data in the Records attached to the speaker and/or bumper Symbols.  If you would post a file containing the Symbols you're using, I'd be happy to take a look.

     

    • Like 1
  12. We use a key system based on the last 6 characters of a user's VW license.  Embedded in a given key is information as to which of our products the user has licensed and which version.  This key is generated each time a user buys a license for 1 or more of our tools.  If a user attempts to use our tools w/o a valid key, the bulk of the OIP is disabled and a button to the tools area on our Web site is displayed.

     

    Does that help???

    • Like 3
  13. 27 minutes ago, Scott C. Parker said:

    Putting per panel weights into the LED screen tool has been suggested and is on our list of wishes for improvement.

     

    This feature is currently part of the Landru Design version of the tool.  Individual module/panel weights can be input, which the tool then uses to calculate, for example, an overall wall weight.  As you change panel counts, the weight updates.

     

    • Like 3
  14. 7 hours ago, MartinBlomberg said:

    I struggle to make an image fit on a wide LED screen. It's a square image and I want it centered on the LED-screen.

    Even though I've unchecked "Tile Image" boxes (Horizontal and Vertical) the image tiles. Since the size of the LED most likely will vary I don't want to have different files.

     

    First:  The way that the tool works is that, in the Edit Array Image dialog, 100% scaling means that the image fills the width of the given screen/array.  If resulting image is than taller than the screen/array, a portion of the image is then not seen/used.  You can use "Vertical Shift" to specify what portion of the image is seen/used.

     

    Second:  The Spotlight version of the tool only automatically tiles the given image. The Landru Design version of the tool adds a "Tile Image" toggle to the above dialog, allowing you to do things like reduce the scale so that you see the entire "taller" image on a wiser screen, center the image (using Horizontal Shift) and not tile the image, as below:

    Tiled.jpg.179ba66a38d580427dd547f664c6016e.jpg

     

    Does that answer your question?

     

  15. 10 hours ago, Sam Jones said:

    OK.  What should the workflow be?

     

    A good question, Sam...

    My initial thought:  Something akin to the way replacing Symbols works - though, more elegant:  Select 1 or more Truss objects.  Click on a "Replace" button in the OIP.  A Resource Selector dialog opens, allowing the user to use that familiar environment to select new truss from a location he/she chooses.  The new truss is positioned using its Insertion Point. and that of the piece it is replacing.  Sections mated to the non-I.P. end would be "pushed out" or "pulled in" if lengths don't match what is being replaced.  If multiple, mated, truss sections are being replaced, replacement sections would automatically mate.  If the user is trying to mate differing truss types, he/she would be presented with an alert/error dialog.  If the resulting length is different from original, an alert/error dialog to that effect would be displayed.

     

    Make sense?

    • Like 2
  16. 2 hours ago, jcogdell said:

    @Ben59
    The replace truss type will only work when both truss type libraries have the same lengths available, from looking at the ST500 library it doesn't include any trusses of the same standard lengths as the sc390 library.
    Normally in this scenario you would select the truss line and use the change configuration button in the truss object properties to change the truss lengths in the line before running the change truss type command, this way the lengths in the line will match what is available in the new truss types library.

     

    ...and...with all due respect...this is another example of the system being WAY more involved to use than it should be...and, of why this needs a SERIOUS re-think.  The more I work with Braceworks-enabled truss, the more frustrated I get.

     

    • Like 3
×
×
  • Create New...