Hugues

@line-weight Yes, data visualization can switch object attributes from hatch to solid and vice versa. You would need to setup appropriate data visualization criteria depending on where your objects are getting their attributes from. Simple example: You have objects in Class A, B and C that are using attribute by class and you want to override the Fill using data visualization. Set the Object Criteria to find objects in class A, B, 😄 Class is A OR Class is B OR Class is C Set the Display Criteria to Objects using function Class. You'll see the list of classes. Set the fill for the classes you want to override to whatever color you like.

The Graphic Legend tool is building the legend for objects and resources that exist in your drawing. There are no criteria for filtering objects based on resources or resource folders in the Resource Manager. You could submit a wishlist item on the Wishlist Forum and describe what you are trying to accomplish.

One possibility is that the 3/4" you are seeing is a rounded display value and that the precise values are slightly different.

Viewport Styles control visibility and attribute overrides for Classes and Layers. You can try to copy a viewport from one file to another to see how the class overrides work. That should give you an idea of how this would work for Viewport Styles.

Edit the reference and you should see the option to auto update the reference at file open. This an option that can be controlled for each reference individually. Note that if you are referencing an image file and the option to save the referenced cache is unchecked, the reference image will always auto update at file open. You must enable "save referenced cache" to control the auto updating at file open. Hope it helps.

You disable the option to auto update references at file open.

Unfortunately, we are not able to replicate it with our test files. If you could provide a simple file that can be used to replicate the issue that would be very helpful. Thanks.

@cberg Annotations should not vanish in the situation you described. It would be really helpful If you could send us a file where you are able to replicate this issue.

Sorry. There was a typo in my previous message: It should read: Your annotations should NOT be deleted because you added a line to the Description title or because of other minor operations...... Does that make sense now?

Your annotations should NOT be deleted because you added a line to the Description title or because of other minor operations. If you have a Legend that exhibits this behavior please report it as a bug and send the file to us for investigation. Annotations are deleted only when fundamentals changed are made to the Legend in such a way that the cells are no longer referencing the objects that were annotated.

This is correct. As of now, Material is the only resource that can be listed in a worksheet database using the standard database methods. Support for other resources will be added in future releases. As @Pat Stanford pointed out, database by script is an alternative method for listing any list of objects in a database worksheet.

Hello Tim, Are you using VW2022? The criteria interface was updated for VW2022 and addressed these issues.

There is an existing bug where the OR condition doesn't work with the LAYER criterion. It works will all other criteria. This is going to be fixed.

Enter the value in the Criteria Dialog with the quotes: ("S" instead of S) It looks like the value of the tag is stored with quotes. This is strange. We will look into that.

@EAlexander Thanks. That is helpful. Could you also provide the graphics card info?

Thanks @EAlexander What operating system are you running? Could you please provide the specs of your machine?

Would you mind sharing the files with us? We want to investigate the issue.

@Bruce Kieffer Have you tried printing the worksheet from its palette?

I understand your frustration and I agree that this functionality isn't intuitive. I'll try to explain how this is designed to work. We are aware of the issues with this design and we will improve it in a future release. The behavior you are seeing is intentional. When you open the "Edit Story" dialog, the list of levels shows: - Levels that present in the story (these have a checkmark) - default levels (unchecked) You can create a new level and add it to your story. Note that this new level is not a default level. Therefore, if you do not add it to the story, it goes away. If you need a level that you can make active in whatever story (these levels are what we call default story levels), you should create by editing your Default Story Levels. A level type is not the same as a story level. You can create a level type from the Level Types dialog. The level types can be used when creating Story Levels or Default Story Levels. I think there is a confusion here that I would like clarify by describing what level types, story levels and default story levels are. Level Type: A Level Type is just a text label that specifies the type of level (e.g. Ceiling, Finish Floor). It has no elevation, no additional properties. Story Level: A story level defines an elevation in a story. It has a level type and an elevation. Default Story Level: Preset story level stored in a list of readily available default presets so that they can be selected and activated in any story. Hope this helps.

Yes, you should be able to assign a Material to a Nurbs surface get quantity takeoff in worksheets.

This is not a normal behavior. I'm not sure why you are getting an error loading the "callouts.txt" database located in your application. This may be because you do not have write access to that database. It looks like that database is your default database. This is why we try to load it by default and since it fails, the process break down. Go to the Notes Manager and change your default database to one you have access to. This may solve the problem. Let us know if this solution doesn't work. In the meantime, we will improve the error messaging when a database isn't accessible.

It appears that those rounding errors are the result of some legacy unit conversions. The width of the row tabs is about 64mm.

S='My Symbol Name' will find all instances of the named symbol in the drawing. You could modify it to isolate a single instance of the symbol. For example you find an instance of the symbol and give it a name, then use (S='My Symbol Name') & (N='name') Or you could place an instance of the symbol in a layer and make sure it is the only instance in that layer, then use (S='My Symbol Name') & (L='layer name') Or you could place an instance of the symbol in a class and make sure it is the only instance in that class, then use (S='My Symbol Name') & (C='class name') Or you can use any other criteria that only one instance (or maybe just very few instances) of the symbol would match.

This is because your criteria is set to find all instances of the named symbol. It will then generate an image for each instance found in your document but will only display one in the cell. That function would need to be a bit smarter and avoid generating images that won't be able to be displayed anyway. What you could do is set your criteria to narrow down the result to a specific instance of the symbol.

These unit and precision of these values are controlled by your document units and precisions. The length unit precision for your document is probably set to 8 decimal places. Are you including the tabs in your prints? Tabs always taken into account even when you turn them off. That would explain why the worksheet doesn't appear centered on the page.