michaelk

@Tom W. Andrea has a free downspout plug-in that does pretty much that. In plan view you drag handles to set the offset and you enter values for the height of the beginning and end of the bend and the height of the gutter. It doesn't do the cool band at the top that you have, however.

That's exactly what a plug-in is for! The built in table and chair tool in VW is exactly that - a scripted plug in that builds tables exactly the way you describe. I'm not sure if creating plug-ins is an addicting hobby or a workflow catalyst (see @Pat Stanford for chart showing when you're enhancing workflow and when you're feeding an addiction). But there are a bunch of people making them and not all of them are degenerate coding addicts. For example, Andrea at https://plugins.andreafacchinello.it makes really great scripted plug-ins that I use all the time for gutters, downspouts, millwork, and beams. (I think I use the beam tool every day for rafter tails, trellises, corbels, etc.) Something like a custom threshold would be a prime candidate for a plug in. It would allow you to have a handle at each end of the threshold so you don't have to do the scaling math :-).

Not that I know of. But you can make a simple script that has all the settings. For example, the ones I just posted ignore volume setting, because it's not something I typically need. But it wouldn't be a big deal to add.

These are the 4 I'm currently using. Let me know if there's something else you need them to do. Set Document Units.vwx Set Document Units v2020.vwx

If you want to play with fire, this little script will convert all the symbols in the drawing to groups. Be real careful 🙂 PROCEDURE Test; VAR OK : BOOLEAN; PROCEDURE ExplodeIt(h:HANDLE); BEGIN SymbolToGroup(h,2); END; BEGIN OK := YNDialog('Are you really sure you want to do this? All symbols will be converted to groups. Think about it.'); IF OK THEN ForEachObject(ExplodeIt,((INSYMBOL & (T=SYMBOL)))); END; RUN(Test);

2021 SP2 added the ability to apply the naming scheme to individual pages. (Thank you, VW!!!!) If you check that box does it do what you need?

I don't think so. You need a 2021 license to open a 2021 file. You can post it here and someone will export it back to 2020 for you.

Does the Clip Tool do what you need?

Works fine here w/ Catalina.

I just tried removing the LW test. In my original script -- that I've been using for years -- it let me declare a variable called LW and use the LW meaning Line Weight as part of a conditional in the criteria. Bone headed on my part. Can't believe that it worked at all 🙂 But using line weight in the criteria does an interesting thing. It only returns objects that can have a line weight. If you just look at objects on the layer or objects that aren't loci then it passes inappropriate objects, like symbols, to the procedure. Better to be lucky than good. Here's a new version: PROCEDURE Test; CONST kLWThreshold = 10; VAR HLyr : HANDLE; LyrNm : STRING; PROCEDURE StompIt(h:HANDLE); BEGIN IF GetLW(h) > kLWThreshold THEN SetLW(h,kLWThreshold); END; BEGIN HLyr := ActLayer; LyrNm := GetLName(HLyr); ForEachObject(StompIt,((INSYMBOL & (L=LyrNm) & (LW<>2)))); ReDrawAll; END; RUN(Test); Looks like SetLW always uses Mils, no matter what the document line weight unit is. This version will only look at the active layer. In my quick testing it handles objects in symbols and in nested symbols!

Thanks @Jesse Cogswell ! I was going to take LW out of the criteria, since it makes absolutely no sense being there. And then do another procedure to find all the reset all the symbols. Might do it tonight depending on how the evening goes 🙂

Ha. I just read this script. Really clunky. If I get a second and @PatStanford doesn't beat me to it I'll make the ForEachObject criteria be not so bad and add a reset for symbols. It's another example of a script where the first time it did what I needed was the last time I looked at it. I've been using it for years not realizing how clunky it is 🙂

So you're finding that the symbols need to redraw after running the script?

Good! I thought I was missing something really obvious. 🙂

Scripts are resources in the resource manager. The main difference between scripts and other resources is that scripts MUST be in folders (called palettes) Copy the text from the post above. In your Resource Manager > New Resource… > Script > Name the palette > Name the script > In the Script Editor window paste the above script. Make sure the language is set to Vector Script. Once it's in your Resource Manager you can right click on the folder and choose open or go to Window > Script Palettes to open the palette. Once it's open double clicking the script in the palette will make it run. Or you can right click on the script in the resource manager and choose run.