Sam Jones

BTW, there is also an AutoPlot script to copy one Lighting Device field value to another, or combine 2 field values into another single field. Usually, used to fill user fields.

It is possible to do by script. AutoPlot Tools has such a script.

If something like the 2 images below works for you, try AutoPlot Tools for Spotlight. sjones@autoplotvw.com

Select the Hanging Position you want to ungroup then go to the "Modify" (in the Spotlight workspace) and select "Ungroup".

Yep. Raymond is. Message him and ask about his "Reshaper" tool.

For those of us that have been participating on this list or its predecessors for more than 25 years, _c_'s departure has been very close to a tragedy. Her understanding of drawing and vectorscript coding is inadequately described as prodigious. She is very kind and was always very generous with helping those of us just starting to venture into coding VS; spending copious amounts of time providing examples and explanations. She is vivacious and funny, and very opinionated. "Vectorworks has an amazing core for the experienced user (and unfortunately a very clumsy usability for the average user)." is a quote from the BIM website cited above While I very much enjoy the Vectorworks community, it was a lot more fun when she was participating.

I would like to convert all the sweeps and extrudes inside a symbol definition to generic solids. Is this possible? I can enter a symbol definition and poll through all the objects and get handles to them, but there seems to be no way to convert them to generic solids. "DoMenuTextByName('Convert to Generic Solids',0);" seems to only work on selected objects on design layers. Is there a way to make the conversion? TIA

Simple, obvious, and I would never have figured that out. Thanks Jesse

I haven't researched this, so we'll have to wait for @Jesse Cogswell or @benghiat to way in. Once you get your plug-in info with: BooResult := GetCustomObjectInfo(PIOName, PIOHan, PIORecHan, PIOWallHan); GetSymLoc(PIOHan, PIOx, PIOy); How about: HRotate(PIOHan, PIOx, PIOy, RotationR) Curious myself, but without immediate need.

One, make a list of the data you want collected for each breaker. Ideally, it all comes from Lighting Device parameters or is computed from those parameters. That will give us the worksheet Two, carefully layout the data for each breaker, spaced to land under each breaker. Each breaker will get a label, but it would be possible to define those labels to be printed as a group on one long label like OnLine 2530 or OnLine 8500. "One" and "Two" can be done separately. "One" will be needed for the script that makes the universal worksheet. "Two" will tell us how to layout the label(s) that use the worksheet. An interesting idea, but I think creating labels for the breaker row of a specific rack is a safer and probably easier way to go. If you have another rack, with different spacing make a label for that rack. One would not need to have more than one worksheet to service all the labels. One label design per specified distro or dimmer rack allows all the measurements of module width, spacing, number per row and other groupings to be baked into the label.

The worksheet cannot be created without a script, but the script is pretty straight forward data collection. Such a script should collect all the data that one might want to list under a breaker in a worksheet row. Different people would use different data for different racks. It would not matter what cell held which information, because those cells would be assigned to label fields, just like the truss tape worksheet. The same worksheet could be used for differently formatted racks that use differently organized breakers; just pick the appropriate label for the appropriate rack. Save the different labels by rack name. The big trick would be the rack header that is at the top of your example. I would be tempted to make a worksheet/label combination that just printed rack headers, but there may be alternatives to that. I retired, and I don't generate labels for anything; I just help people do it with plug-ins. Help with rack and distro labeling is often requested. I'll do it, but it would require a significant input from users (you). I need data specification, the data you want and how you want it, and specific rack breaker space dimensions and/or specific label choices and label formatting of the data. If you want to do it, I'll go there (also true for anybody else), but there will be some significant back and forth. Usually, responses to me about this sort of thing die on the vine; nobody has the time. The goal here is to create a script for creating the worksheet, and then creating the appropriate labels. Of course, you wouldn't have to print on labels; you could print on regular paper and cut it up. I can't even get riggers to give me simple examples of the labels they would need, and that is after I volunteered to create the labels and the appropriate worksheet creation commands.

@Cookie_NZ Is the Excel sheet printed on label stock, or is it printed on regular paper, cut up, and taped below the breakers, or not cut up and taped to the rack? Are the Excel sheets generated separately on a per rack basis, or is an Excel sheet generated that contains all racks?

@Cookie_NZ if you can provide a worksheet, I can provide a way to print the worksheet cells onto Avery or Online labels. Let me know if you want to Zoom.

Might work. Ick.

I want to import a record, and if the record already exists, I want to check the number of fields in the existing record with the number of fields in the importing record in the callback procedure of "ImportResToCurFileN". Since both records will have the same name, how do I do that. Getting a handle to each and using the "NumFields()" function would work, but since the records have the same name, how do I get a handle to each or is there another way to query the number of fields in each record definition of the same name? How does the callback procedure specify whether or not to import the incoming resource? TIA.