markdd

Hi Scott - I was referring to reference symbols inside accessory symbols. These are used to define non-standard placement of accessories to Lighting Devices. For instance, an iris fitted to a Lustr would usually be shown at the gate position. However, the Accessory tool will insert it at the front of a Lighting Device by default unless the user adds a reference symbol to the Accessory, which will define the automatic placement position. It is this reference symbol that shows up in the Equipment Summary which most users do not want to see. The suggested new line in the help file would advise users to remove the reference symbol which will mean that when the reference symbol is removed, the already placed accessories will revert to the default position at the front of the lighting device. Currently, the only foolproof way of using accessories alongside the Equipment Summary Key (that have found) is to make all custom placements manually using the 'Edit Accessories and Hardware' button found in the Object Information Palette of the Lighting device. It would be ideal if the Equipment Summary object could filter out reference symbol geometry and just show the Accessory geometry. I've attached a file that will show the problem if the reference symbol is removed. Accessory conundrum.vwx

The trouble with telling users to remove the reference symbol before making an Equipment summary is that the accessories that are added to lighting devices will move back to their default positions. Surely a better solution would be to give the Equipment Summary the wherewithal to know which objects represent is the accessory geometry and which represent the Reference symbol.

Snapping is the key. If you don’t like snaps all the time, you can temporarily suspend them with the “ backquote” key.

No, I'm afraid not. You will need to add the Chord Snapping geometry manually for each Truss Chord. This consists of a 3D Polygon with the Chord Snapping Record format attached. To learn how to do this, you should import a current Truss Symbol from the libraries and reverse engineer the class and data record settings that will be loaded with the Truss symbol.

I'm interested in what you are suggesting, and I agree that the finished object should have more parametric functionality. The ability to swap one profile for another in the Object Information Palette using 2D shape symbols could be useful. Perhaps the option to copy a profile shape rather than using it. This would mean that one wouldn't need to make endless copies of profile shapes. Perhaps there's a better way to adjust the profile's position. Currently, the reshape tool does a good job of adjusting the path. What could a tool do over a command? I imagine that the ability to select an existing edge profile could be helpful in a combined workflow?

The only way I know how to do this is to set up a 'Spare' field in a record attached to the objects or a User Field on the objects you are numbering, and then paste a number sequence from another Worksheet Column or an external spreadsheet app such as Excel or Numbers. At least that way, you will be able to arrange your objects in the order that you want them in the Worksheet and then paste the number sequence in the correct order.

I think what you are asking for is possible. Can you clarify a little more what the final outcome should be and where you would like the mapped data to end up?

Could you be clicking on the wrong row - it looks like you are clicking on Row 1. The Database header row is Row 2.

Then pick Edit Report, which is just above.

Right-click on the column cell next to the Worksheet Database Row header and select Edit Criteria from the menu. or press this button.

If you have a quantity of connected or intersecting NURBS surfaces that you need to be re made into solids for modelling, then use the Stich and Trim command.

You can save a formatted Symbol Key object as a red Plug-in Symbol. That will hold all the formatting which saves a few steps when creating these.

No, I'm afraid not. You can do it in a worksheet though.....

This is what I have used, and it works perfectly. What are your document units? Maybe you should be adding more than just 0.300?

This is how it could work just using Data Visualization. Enclosed is the file. Data Vis.vwx