Target Attribute pulling info from source attribute, target attribute not editable

[gccdesign]

After much frustration, but fortunately my determination won, I have created my first block that has one attribute being the source for the data in other attributes in the same block.

The purpose for this is that I want the block to be reversible, and the attribute text fields get the justification scrambled if you just flip them.

There is a certain procedure when inserting this block that apparently must be followed.

Insert the block. Fill out the two "source" fields, do not fill out the "target" fields, and accept.

Back into model space, after the block insertion dialog box is done, grab a stretch handle and nudge it, or put it where you want. Apparently activating a dynamic handle activates the target text fields to wake up.

Now, "RE" for regen, then "Enter". It will update the target fields. (this won't work in the _TestLVL)

After this you can flip with the visibility control or enter new values in the "source" fields, regen (RE) and it will update the target fields.

The source fields show in model space and so on, but are on a non-printing layer.

But here is my question. I have tried to turn on the "constant" property for the target fields, but it stops them from updating. (See the _TestLVL block)

I don't want the target attributes to be visible to the users. Any ideas?

GChapp

[Libbya]

Not really any good ideas.  You can place the attributes you don't want edited onto a locked layer.  The attribute editing window will no longer pop up but you can edit the unlocked attributes in properties.  Unfortunately, the justification of right justified attributes will be messed up with the change of length.  To fix the justification, you need to unlock the layer, then relock it.  You could also use User Parameters set to string type to house the values.  Those values would be edited in properties also but the attributes housing the fields could still be edited in the attribute editor and messed up by users.  If you do not need custom attribute values but instead can get by with specific values from a list, you could do that using a block properties table writing the values directly.   Pick your poison.