Topic: Attdisp Normal vs ON

[David Hall]

OK, this is totally baffeling me.  I have 2 instances of the same block, 1 has an attribute visable, one does not (in Normal mode).  If i set attdisp ON, they both show.  If I go back to Normal, only one shows.  How is this possible?

[mjfarrell]

Attribute modes control the behavior of attributes in blocks. For example, you can control

Whether an attribute is visible or invisible in the drawing
Whether an attribute has a constant value, such as a part number
Whether the attribute can be moved relative to the rest of the block
Whether the attribute is a single-line attribute or a multiple-line attribute
If an attribute has a constant value, you will not be prompted for its value when you insert the block. If an attribute has a variable value, such as the asset number of a computer, you will be prompted when you insert the block.

fix with BATMAN

You can edit the values and other properties of all attributes that are already attached to a block and inserted in a drawing.

You can modify attributes in block definitions with the Block Attribute Manager. For example, you can modify the following:

Properties that define how values are assigned to an attribute and whether or not the assigned value is visible in the drawing area
Properties that define how attribute text is displayed in the drawing
Properties that define the layer that the attribute is on and the attribute line's color, weight, and type
By default, attribute changes you make are applied to all existing block references in the current drawing.

[mjfarrell]

by hep file definition:


Normal
Restores the visibility settings of each attribute. Visible attributes are displayed. Invisible attributes are not displayed.

On
Makes all attributes visible, overriding the original visibility settings.

Off
Makes all attributes invisible, overriding the original visibility settings.

[David Hall]

yes, I got all that, but how can it be 2 different ways at the same time?  DL the file and look at it

[mjfarrell]

someone edited one...and did not sync things up

Update Block References

You can update attributes in all block references in the current drawing with changes you made to the block definition. For example, you may have used the Block Attribute Manager to modify attribute properties in several block definitions in your drawing but elected not to automatically update existing block references when you made the changes. Now that you are satisfied with the attribute changes you made, you can apply those changes to all blocks in the current drawing.

You can also use ATTSYNC to update attribute properties in block references to match their block definition, or to update a block instance after you redefine a block attribute using BLOCK, -BLOCK, or BEDIT.

Updating attribute properties in block references does not affect any values that have been assigned to those attributes.

[David Hall]

I see what your saying, but what a PITA that would be.  That means they would have to insert 6 of these blocks, then edit the definition, and insert the next 200.
and its not just 1 drawing, but like 125

[David Hall]

someone edited one...and did not sync things up

Update Block References

You can update attributes in all block references in the current drawing with changes you made to the block definition. For example, you may have used the Block Attribute Manager to modify attribute properties in several block definitions in your drawing but elected not to automatically update existing block references when you made the changes. Now that you are satisfied with the attribute changes you made, you can apply those changes to all blocks in the current drawing.

You can also use ATTSYNC to update attribute properties in block references to match their block definition, or to update a block instance after you redefine a block attribute using BLOCK, -BLOCK, or BEDIT.

Updating attribute properties in block references does not affect any values that have been assigned to those attributes.

Also, I tried to do what you did in RED, and cannot.  How would you do that?

[mjfarrell]

sounds like it could have happened just that way...

...could be a training issue (I'm sure you folks have standards)
...could be careless
perhaps instead of using normal EATTEDIT, they used the block editor to edit the attribute values?

[mjfarrell]

someone edited one...and did not sync things up

Update Block References

You can update attributes in all block references in the current drawing with changes you made to the block definition. For example, you may have used the Block Attribute Manager to modify attribute properties in several block definitions in your drawing but elected not to automatically update existing block references when you made the changes. Now that you are satisfied with the attribute changes you made, you can apply those changes to all blocks in the current drawing.

You can also use ATTSYNC to update attribute properties in block references to match their block definition, or to update a block instance after you redefine a block attribute using BLOCK, -BLOCK, or BEDIT.

Updating attribute properties in block references does not affect any values that have been assigned to those attributes.

Also, I tried to do what you did in RED, and cannot.  How would you do that?

that is straight from HELP file...I did not attempt to perform....

[MP]

Eack block instance enjoys its own collection of attributes. You know this because each non constant attribute sports its own state. That "state" extends beyond the value of the textstring property (dxf group 1) to the visibility / constant states etc (dxf group 70), the tagstring (dxf group 2) etc.

I've exploited this for years, creating as many attributes as I need per block instance (yes, you can vary the number, type and tags of attributes between instances of the same block def) toggling attributes between read-only | write-able, visible | invisible etc. on the fly, at will.

If I wasn't on my blackberry I'd post some sample code but alas.

[T.Willey]

Attributes have an invisible property which can be true or false.  Here is a string of code that you can run to see what they are set to.

I wrote the code as one line, so that you can just hit the up arrow to use again in Acad.

Code: [Select]

(foreach i (vlax-invoke (vlax-ename->vla-object (car (entsel))) 'GetAttributes) (prompt (strcat "\nTag = " (vla-get-TagString i) ", Invisible = " (vl-princ-to-string (vla-get-Invisible i)))))(princ)

Returned for the left block

Tag = TERMDESC02, Invisible = :vlax-true
Tag = TERMDESC02A, Invisible = :vlax-true
Tag = WIRENO02A, Invisible = :vlax-false
Tag = WIRENO02, Invisible = :vlax-false
Tag = P_TAGSTRIP, Invisible = :vlax-false
Tag = WIRENO01A, Invisible = :vlax-false
Tag = TERMDESC01, Invisible = :vlax-true
Tag = TERMDESC01A, Invisible = :vlax-true
Tag = WIRENO01, Invisible = :vlax-false
Tag = DESC1, Invisible = :vlax-false
Tag = INST, Invisible = :vlax-true
Tag = TERM, Invisible = :vlax-false
Tag = FPT, Invisible = :vlax-true
Tag = LOC, Invisible = :vlax-false

Right block

Tag = TERMDESC02, Invisible = :vlax-true
Tag = TERMDESC02A, Invisible = :vlax-true
Tag = WIRENO02A, Invisible = :vlax-false
Tag = WIRENO02, Invisible = :vlax-false
Tag = P_TAGSTRIP, Invisible = :vlax-true
Tag = WIRENO01A, Invisible = :vlax-false
Tag = TERMDESC01, Invisible = :vlax-true
Tag = TERMDESC01A, Invisible = :vlax-true
Tag = WIRENO01, Invisible = :vlax-false
Tag = DESC1, Invisible = :vlax-false
Tag = INST, Invisible = :vlax-true
Tag = TERM, Invisible = :vlax-false
Tag = FPT, Invisible = :vlax-true
Tag = LOC, Invisible = :vlax-true

[David Hall]

I know that I can set the visability status on entities, my problem is the company I got this from, I dont think they are smart enough to do this.  So mostly I am trying to figure out how they could have done this with out of the box autocad

[David Hall]

I've exploited this for years, creating as many attributes as I need per block instance (yes, you can vary the number, type and tags of attributes between instances of the same block def) toggling attributes between read-only | write-able, visible | invisible etc. on the fly, at will.

But if I understand what your saying, you do this through code.  Can it be done w/o code?

[T.Willey]

I think Acad Elec has some OOTB lisp routines that one can use to make attributes in/visible.  If that helps at all.

FYI..... Attributes have the Invisible property, and the Visible property.

[David Hall]

Tim, can you get to the visible property w/o code?