Pat Stanford

Have you tried the Reset All Plug-in Object command from the Tools:Utilities menu? That should make them reset. And if you are only doing it occasionally after running the Classing PIO, then the delay should be tolerable.

Have you updated to Update 2 that was released just before Thanksgiving. I think at least some of the issues you mentioned were fixed there.

The check box is just a field in the Plug-in Object Parameter Record. Find the right field and you can set or unset it the same as you would change any other field in a record. But before you go there, you probably want to take a look at the Graphical Legend too/object. It is designed to do exactly what you are trying to do and will prevent you having to place extra plants into the drawing to get the legend you want.

Yes, that is a Warning and should show in Developer mode only.

Seriously, there are ways to help automate classing (I am not enough of an expert to be able to offer the best ways as I work almost exclusively solo), but it is going to be very hard to "force" everyone to do the right thing. When they feel rushed they are going to do what they think is fastest, regardless of the issues that causes down stream. I think @michaelk has a bunch of worksheets that he uses to audit drawings and show things that are in the wrong classes. Maybe something like that would help for you?

Correct what I have posted draws from the defaults of the record format. Does not matter if the record is also attached to an object, it will always draw the defaults. The Data Tag will not be able to pull from some other object in the drawing, only the object that it is associated with. To get that data all you need is to use the Record.Field options in the Data Tag Dynamic Text.

Your best option is probably Pink Slips for those who don't comply. 😉

You are going to have a very hard (Read as almost impossible) time getting a data tag to read data from another object. Data Tags are designed to return data from the associated object only.

You are correct that it is the GetBBox that is causing the problem. As you rotate the object the bounding box expands as the BBox is always vertical/horizontal. Either use Sin/Cos to calculate the end point of the first/ start point of the second (x change and y change) or use Raymond's idea and use Vectors.

'Circuit'.'CableLength' returns a string. In this case you are checking that the string stored in that field is the string '30' In Cell A1 you have stored a number of 30. A number 30 is different than a string of 30. You can cover the Number 30 to a string by using the TXT() function. ='Circuit'.'CableLength'=TXT(A1) HTH

As a first step what I think might be useful would be a function to return the Layer of the "Parent" object of the Data Tag. So if it was in a Symbol, it would look at the Symbol Instance and report the Layer the instance was on. If you used this function it would not operate properly in a Data Tag that was on a Layer and not part of a symbol. But this limited functionality might make it easier to generate the requested data.

Normally in a case like this the worksheet is generated based on the data in a Record.Field attached to an object in the drawing. But the current limitation to VW is that whatever data is in the Record Definition when the record is attached to the object in the drawing is the data that is attached to the object. If you later change the default values in the Record Definition those values do not propagate to the instances already in the drawing. This is a "good thing™" because this is what allows you to have different values for different instances. But it does make it difficult when you are trying to keep a field value in sync between multiple objects. All of the ObjectValue formulas I worked out above just give you a way to use a Record Definition as a "single source" for values for multiple data tags.

The attached file shows a data tag using a couple of different IF methods to access different data. The file has a record format names Test1. It has Fields: Red, Blue, Other. The data tag is set up the way it is to kind of show how I go about creating complicated data tags. The top text block has what we figured out a couple of days ago about how to pull data from a record format. This is there so I could make sure I knew what the value of the Color field is. The middle text block has Five lines using a WS_IF statement. This started out as a single line, but I was having trouble getting the quotes and parentheses right. So I simplified the first line to make something more basic work. Then I started extra lines making each more complicated until I got the result I wanted. The bottom text block uses what I learned in the second, but it uses and #WS_FIS( function. In worksheets and data tags, the IF function takes a single logical results and returns one value if there logical is true and another if it is false. You can next multiple IF statements if necessary. IFS is similar to IF, but it takes multiple sets of Logical and Result if that logical value is true. The logicals have to be surrounded by Parentheses. The Results have to be either a string constant (ie surrounded by single quotes) or a function that returns a text value. The benefit of IFS is that you can put multiple different logicals into a single function while returning multiple different values. The first logical that returns true will determine the Result that is returned. If the last logical is (ELSE), then anything that does not match any of the logical statement will have the last Result returned. Hope this makes sense. Because you have use such long statements for both the Logical and Result for the "references record" thing we are doing, they get hard to work with quickly. Getting all the parentheses and quotes straight is a challenge. Data Tag WS_IFS.vwx

How about the Paint Bucket (Inner Boundary Mode) of the 2D Polygon tool?

How about just 2024.2?

Try and create a new file (from your template is you have one). Check and make sure it is not turned off in the new file. If it is you need to create a new template file. You can just change the Unified View in a new file opened from your template and resave it as a template. Or if it is old (several versions or more) you might want to recreate it from scratch.

Please report back if you find something that works. We all need the information.

@Peter Telleman =Value(OBJECTDATA('INVENTORY PART PARAM', 'Curtain', 1, 5,)) Should do what you want.

@JBenghiat I completely agree with you on using handles instead of Selection. I have not tried, but could it be said (In this use case) that DeleteObjs basically only works on Visible Selected Objects? That objects inside symbols (where the object is selected but the selection state is not visible) are not deleted?

I don't understand. You have a worksheet and and image of the worksheet on the drawing. Now you want to replace the image of that worksheet with an image of a different worksheet? The two different worksheets happen to be formatted so they have the same dimensions? A use case would help explain whaat you are really trying to do.

Duplicate the file and delete the Sheet Layer you don't want them to have?

1.1 was released to fix a single bug that was preventing the 1 update from working properly for a percentage of people. 1, 2 are the standard update numbering. You shouldn't see X.1 etc. very often.

Model Menu: Volumetric Properties. If you want this to display all the time in the OIP, you would be better off making a post in the Wish List Forum.

Check the Document Preferences:Legacy 2D pane. and make sure that Turn Off Unified View is not checked. If it is, then each Design Layer has its own view settings. With Unified View turned on, when you change the view of one layer then all the active layers (at least ones with the same scale) change views at the same time.