Jump to content

Benson Shaw

Member
  • Content Count

    3,490
  • Joined

  • Last visited

Community Reputation

399 Spectacular

About Benson Shaw

  • Rank
    Vectorworks Addict

Personal Information

  • Occupation
    Public Artist
  • Homepage
    www.bensonshaw.com
  • Location
    United States

Recent Profile Visitors

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

  1. @rDesign Doh! Thanks. I’m being oblivious again. Keying on autopilot. @ web team, et al, Never mind -B
  2. @forum web team Please add "Design Layer Viewport" as a roll over popup for "DVLP" abbreviation in community board posts. Probably need to add some other abbreviations, too. Thanks! -B
  3. Oh, Sorry! Yes, (xxxx edit) DLVP is Design Layer Viewport. -B
  4. Several ways to do this with DVLPs: 1. Keep it all in one file. • Create a new blank layer. • On this layer create a DVLP with its layer visibility showing only the layers containing arch elements. (nothing else should be present on this DVLP layer) • Adjust the DVLP xyz to match the required location and elevation • Adjust the overall drawing file layer visibility to hide everything except layers with the site elements, and the DVLP. • For Sheet Layer ViewPorts showing both arch and site, adjust OIP layer visibility as needed to show the site and the DVLP layer (not the individual arch layers). • Other SLVPs may not need to show the DVLP. OR . . . 2. Split the project into two (or several) separate files, eg architectural elements, and site elements. • Choose one to be the "Project" file (probably the site). • In the Project file, create a new design layer and make a Design Layer Viewport in this layer referencing the other (probably architectural) file. • This DVLP can be moved in xyz as needed. • Additional DVLPs can be created on different layers if different visibilities are needed • Any saved changes to the arch file will cause the DVLP to be out of date, so update the DVLP to show the changes: Navigation or Organization Palette>Reference tab>Right click item in the list & choose Update. • DVLPs do not add their classes and layers to the project file. But, the DVLP Layer/Class visibility is controlled in its OIP dialog. • If a Sheet Layer VP needs different layer/class visibility of one of the DVLPs, Duplicate the DVLP layer and adjust visibility in the dupe OIP, then show the dupe layer, rather than the orig, in the SLVP. OR . . . 3. Present the project in a Master File. More elaborate version of #2. • Master file is blank, except it contains layers for DVLPs of arch, site and any other files • Master file is where all the Sheet Layer VPs are created and annotated. HTH -B
  5. I think this is good strategy. Also, sometimes it can be helpful to edit an existing solid subtraction containing several subsequent nested operations with goal of reducing the number of nest layers. But work on a dupe object for safety. Eg (A+B) -C-D-E can be converted into (A+B) -(C+D+E) - Dbl click repeatedly to access the E layer edit space. - Select all, copy>delete or cut (empties the E layer) - Exit the E layer (now drawing is in the D edit layer, E ceases to exist) - Paste, then select all>cut (empties the D layer) - Exit the D layer (D is gone, drawing is in C edit space) - Paste (everything from CDE in same edit space) - Exit, exit as needed to return to drawing space Not always useful but can relieve some confusion in a deeply nested object. Probably more useful for combining nested solid addition layers than for subtractions. That’s for sure! @lineweight great question! -B
  6. @mjm Just remembered something else about that no-select glitch. Maybe mine involved a name conflict (and several vwx files open). Might have been a saved view with same name as a design layer or a class? I thought it might be repeating an existing name when I made it, but for some reason the usual error message did not occur at time of creating the conflict name. Then the drawing went wonky, so I looked at the names. Added a dash, or deleted a space between words in the saved view name. Select tool resumed usual functions. Tried to force the problem in new v2020 files. No success, but these new ones are simple files with only a few objects, views, etc. Anyway another possible cause in the problem file. Hope you sort this. -B
  7. I needed a catenary in vwx to describe a cable hanging between two posts. I drew a poly line cubic spline - top>midpoint>top. Then I found an online catenary generator, input the parameters for same span and sag, saved the resulting pdf image and ported that into vwx. The spline fit on the image. Same process confirmed spline fit to image if post tops not same height. Math correct? Not sure. But close enough for my use. -B
  8. Reboot? does marquee select act differently? l saw a similar selection glitch in v2020 SP1. Can’t reproduce now. I think I had 2 files open. Separate windows rather than tabs. Switching between them might have caused the problem. Anyway Save/Close/Reopen file, or Save/relaunch vwx, or system reboot solved it. I will try to track it better if it recurs. -B
  9. Marionette node input/output text labels can be obscured by the node gradient fill when drawing is toggled to black background. Wish is for a separate control/class of the wire color so that text can be black (or dark grey) when drawing is in black background. And wire can switch from black to white. Setup General condition when toggling black/white backgrounds is that "pure" white and black attributes switch. Dark grey (impure) does not switch. Marionette nodes have a gradient fill - white to a color (different color for each node type) Node input/output text labels are same class as wires. Label pen color for white background is black, and switches to white in black background. If pen color of a node is changed via class or attributes palette, any wires for that node change to same color. Separate classes for labels and wires would allow always dark text (dark grey), AND wires always opposite of background color. -B
  10. Marionette node for Rotate Line rotates the result in clockwise (negative) direction. Basic wish is for script to be altered to cause counterclockwise (positive, anti-clockwise) rotation. More elaborate wish is for user control of rotation direction, either via input port, or, better, OIP control. As @GRZEGORZ points out, the script for the node uses a "-rot" element. Change that to "rot" and the resulting line rotates in positive direction. Current version may be WOD. I don't know why we want negative rotation. I filed a bug, too. -B
  11. @GRZEGORZ Thanks for looking into this!!!!! And posting a solution!!! @all, esp vwx folks This node appears to be Working as Designed (WOD), but I think rotation should default to counter clockwise. What is logic behind the choice of clockwise rather than counter clockwise rotation? I can customize the script, but will need to change every existing instance of the node. and keep a customized one in library. I filed a bug and a wish for choice of direction in the standard Rotate Line node. OK, any further comment appreciated. -B
  12. Rotate Line rotates in wrong direction. Usual convention is anti clockwise rotation for positive angles. Sample network uses only nodes from v2020 default library. Pilot error? Node bug? Thanks -B Rotate Line Test v2020.vwx
  13. This is why you are in management and I'm a clerk in the mail room. I'm just starting to explore Marionette. Great to have comment and mods from a master. I tried several ways to find/report the length of list (number of items). I might have tried (possibly incorrectly) the Add List. I think it was returning a value of 1 for each item in the list, but not adding the ones. Or something. No, the prime numbers are uniques in the list. Any item in the list has a greater value than all of its preceeders and smaller value than all of its followers. Same behavior in the integer list. If I change parameters, via slider or key, in your cool modified SB Marionette object, an error dialog is generated. If I choose either Close, or Select Node, the dialog closes and the M Object updates to the new values. ??? Note, just started using v2020, so looking at translated file.
  14. Isn’t the command working as requested? It replaces any selected object(s), not just symbols, with the chosen symbol. -B
  15. @line-weight Right. I couldn’t tell from OP whether the problem is DL objects or VP annotation objects. Hence my essay about intent and function of those scale options. Let’s ask for some clarification: @Danilo could you please elaborate a bit? Are you trying to adjust line type scale of objects in the VP annotation space? Or design layer objects shown in the VP? Can you post a file here or a screen shot showing the problem. -B

 

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