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?

[T.Willey]

I don't see a way OOTB to change them once they are inserted, but you can change the ' attribute ' of the attribute definitions with ' battman '.  If you hit the ' edit ' button, the first tab is ' attribute ', and there is an ' invisible ' mode there that you could un/check.  I didn't see another way in '09.

[MP]

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

Do not underestimate the ability of the garden variety idiot to use code found on the internet he cannot write and similarly does not understand, neither in construct nor use.

[MP]

Can it be done w/o code?

Not so much, unless you consider tools, like ET etc. to be created "w/out code".

[David Hall]

ET? I dont have ET as a command

[Kerry]

[WAG]

ET=ExpressTools

[MP]

[WAG]

ET=ExpressTools

[●] correct
[ ] incorrect

[David Hall]

Express Tool, DUH!  I was thinking of the very old text editing command ET

[MP]

Couple drawings to demonstrate variable attribute properties.

ATTRIB_Example_1.dwg
ATTRIB_Example_2.dwg

Drawings are identical except for one thing.

[David Hall]

MP, you did that through code?  Very cool

[MP]

Yes sir + thanks.

[Crank]

You don't have to do that through code. Change the properties of the attribute with the BEDIT command and insert the block again.

Nb. I also think it's dangerous to change attributes so they are different from the block definition: If someone uses ATTSYNC on that block the result could be affecting other (overlooked) blocks as well.
So if you want to do this through code, your program should have to replace the original block with a unique copy (something like Autodesk did with dynamic blocks: after the properties have changed they are replaced with an unnamed version of that block).

[MP]

I also think it's dangerous to change attributes so they are different from the block definition: If someone uses ATTSYNC on that block the result could be affecting other (overlooked) blocks as well.

I've used the technique successfully for more than double the years that I've been on this board. It's as dangerous as placing any info in the drawing users can modify or delete.

[Krushert]

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

Do not underestimate the ability of the garden variety idiot to use code found on the internet he cannot write and similarly does not understand, neither in construct nor use.

Did somebody call my name? 

[David Hall]

MP, what language are you using to edit those attributes?  Its funny how things happen.  I asked this question last week or so, and yesterday the BIG boss came by and said they were having a meeting about the titleblock and blah blah blah.  Bottem line, I have to make it so the users cannot edit the first line of the title block.  So Im thinking make it constant , somehow using what you have described.

thanks

[MP]

Vanilla LISP (entmake or DXF modification). The applicable properties are read-only to ActiveX, so vla-* yada will not work, neither will VB(A). I'll post some applicable code when I can sneak some time.

[David Hall]

any chance .Net can touch it?

[MP]

Doubtful, as I would guess the .NET interface honors the same intent as the ActiveX interface, i.e.the Constant property etc. is read-only.

However, if you go thru an ObjectArx wrapper you could probably make them squeal like a pig.

[T.Willey]

Doubtful, as I would guess the .NET interface honors the same intent as the ActiveX interface, i.e.the Constant property etc. is read-only.

Confirmed.  I couldn't even compile the code when trying to change the IsContstant property.  Just a quick test though.  Didn't try anything else as a work around.

[David Hall]

BUMMER, ok, I have to ask, can you post the LISP code?  Its been forever since I did any lisp, so I will spend more time floundering than its worth at this point.

[David Hall]

My other question might lend itself to the discussion, How could I insert a block with attributes, use code to fill out the constant, or if its not constant, lock it from editing

[T.Willey]

To make an attribute constant, change dxf code 70 to 2.

(setq ent (entget (nentsel)))
(entmod (subst (cons 70 2) (assoc 70 ent) ent))

You can still change the contents with code.
(entmod (subst (cons 1 "test") (assoc 1 ent) ent))

Hope that helps.

If you want to insert a block with attributes, then you have to create all the items with dxf codes.  If you want it easier, then you can use the ActiveX way to insert, then just edit the attributes with dxf codes after.  Ron just posted a routine to create a block within a drawing, as block I mean insert.
[ http://www.theswamp.org/index.php?topic=33237.0 ]

Edit:  Add the bit code for code 70 of attributes.

70
 Attribute flags:

1 = Attribute is invisible (does not appear)

2 = This is a constant attribute

4 = Verification is required on input of this attribute

8 = Attribute is preset (no prompt during insertion)
 

[MP]

You can do it at least 2 ways Cmdr. You can entmake the attributes when you entmake the block instances, setting the constant flag in the 70 group or you can set the constant flag in the 70 group after the block instance and the attribute(s) are made. What you do not want to do is define the attribute of interest as a constant attdef in the block def. When you do that said attribute is common to all block instances of that block. Clear as mud?

[MP]

To make an attribute constant, change dxf code 70 to 2 ...

Keep in mind you want to perform a bitwise or, using the existing group 70 value and 2:

(logior 2 (cdr (assoc 70 dxfdata))) ...

If you set it to 2 you could unwittingly nuke the invisible state etc.

[T.Willey]

To make an attribute constant, change dxf code 70 to 2 ...

Keep in mind you want to perform a bitwise or, using the existing group 70 value and 2:

(logior 2 (cdr (assoc 70 dxfdata))) ...

If you set it to 2 you could unwittingly nuke the invisible state etc.

Yea.  That's why I edited my post to show the bit codes for dxf code 70.  Thanks for stating it clearer.  I forgot we are not in the lisp forum.

[MP]

I knew you knew Tim, was just making sure the audience greater was informed.

And for the audience greater, to "mask off" the constant bit do this:

(logand -3 (cdr (assoc 70 dxfdata))) ...

or this if you don't like "magic" numbers:

(logand (~ 2) (cdr (assoc 70 dxfdata))) ...

Keep in mind you do not have to revert the attribute to a non constant state to change the attribute's value (dxf group 1 | activex property 'textstring) from code, using either dxf or activex methods.

[David Hall]

mud, definetly mud.  I will have to get back to you on this.  At least I know I can do something, just not sure what yet.  Thanks