Linked Attributes, Dynamic Block Vis states

[Chris.N]

Has anyone experimented with linking 'constant' attributes with a master group of 'invisible' ones?

what i am trying to accomplish is have left / right vis states (with appropriate justification) but have it linked to the 'editable' attributes. the logic is that i only have to edit once for all vis states of block.

i have already searched for "linked, attributes" and am kind of trying to expand on Mark D's blog method (using lookup tables) into something completely custom editable.

Thanks!!

[Rico]

Has anyone experimented with linking 'constant' attributes with a master group of 'invisible' ones?

what i am trying to accomplish is have left / right vis states (with appropriate justification) but have it linked to the 'editable' attributes. the logic is that i only have to edit once for all vis states of block.

i have already searched for "linked, attributes" and am kind of trying to expand on Mark D's blog method (using lookup tables) into something completely custom editable.

Thanks!!
Hey Chris, did you ever find a solution to this dilemma?

[Chris.N]

Hey Chris, did you ever find a solution to this dilemma?no, but i may have stumbled upon my flipped diagonal (http://forums.augi.com/showthread.php?p=349903#post349903)line one in another thread i made.

[Rico]

no, but i may have stumbled upon my flipped diagonal (http://forums.augi.com/showthread.php?p=349903#post349903)line one in another thread i made.
What did you find?

[Chris.N]

What did you find?after looking in the mirror, an idiot....

check it out

[jgratton]

Hey Chris, did you ever find a solution to this dilemma?

I'd be interested in a solution myself. Seems you can't flip attributes. How sad!

[Chris.N]

I'd be interested in a solution myself. Seems you can't flip attributes. How sad!i haven't found the solution yet, but you can flip attributes, but the justification will stay the same

[jgratton]

How would you handle a situation like this? The geometry has to have capability of rotating in 90 degree increments. The attribute has to be available in all 3 visibility states and moveable when the object is in 90 and 270 degree positions. The two texts are each visible in their own respective states, and must also move when the object is rotated to 90 and 270 deg positions.

I am having trouble getting the attribute and text to move when the object is rotated.

The fact that I could not find anything similar on the provided tool palette leads be to believe the capability is not yet there.

I hope someone can prove me wrong.

[jgratton]

I am having trouble attaching things (the pop-up blocker keeps coming up even though I disabled it)

The attachment should be with this.

[whdjr]

If you want to move your text while rotating (but not rotate the text) then you need to set a point parameter for the text and include only the point parameter in the rotation action. Then you need a move action for the text to the point parameter. The point parameter needs to have the 'Chains' property set to Yes.

Does that help?

[whdjr]

Has anyone experimented with linking 'constant' attributes with a master group of 'invisible' ones?

what i am trying to accomplish is have left / right vis states (with appropriate justification) but have it linked to the 'editable' attributes. the logic is that i only have to edit once for all vis states of block.

i have already searched for "linked, attributes" and am kind of trying to expand on Mark D's blog method (using lookup tables) into something completely custom editable.

Thanks!!Chris,

Can you post your block. I have a concept I want to try out.

Thanks,
Will

[Chris.N]

Chris,

Can you post your block. I have a concept I want to try out.

Thanks,
Willi got ticked and junked it.

here's an illustration of what i want to do. the right and left attributes are vis state controlled, but non-editable because of being linked to the master attribute for the content. The master attribute would be invisible. for some reason, i can't get the fields to work in this way.

[Rico]

I am having trouble attaching things (the pop-up blocker keeps coming up even though I disabled it)

The attachment should be with this.
still no attachment. try again.

[whdjr]

i got ticked and junked it.

here's an illustration of what i want to do. the right and left attributes are vis state controlled, but non-editable because of being linked to the master attribute for the content. The master attribute would be invisible. for some reason, i can't get the fields to work in this way.If I understand you correctly you want it to show two attributes but you only want to edit one and have the other update from the one you editted. Is that a correct assumption?

[jgratton]

still no attachment. try again.
This is frustrating. I have tried the internet options, even made AUGI an exception to pop-ups. I tried lowering my privacy settings.

I used to attach all the time from work. Something with this laptop setup is different.

[Chris.N]

If I understand you correctly you want it to show two attributes but you only want to edit one and have the other update from the one you editted. Is that a correct assumption?sort of. this would be my work-around untill flipping attributes also flips it's justification. left and right would only be shown individually. what it's for is an elevation marker for architectural elevations and sections. I want one block, but for both right and left sides. I don't want to have to re-input the info after flipping.

how's that?

[whdjr]

This is frustrating. I have tried the internet options, even made AUGI an exception to pop-ups. I tried lowering my privacy settings.

I used to attach all the time from work. Something with this laptop setup is different.Are you using Firefox or IE? I couldn't get mine to work in Firefox so if I attach a dwg I do it in IE.

[whdjr]

sort of. this would be my work-around untill flipping attributes also flips it's justification. left and right would only be shown individually. what it's for is an elevation marker for architectural elevations and sections. I want one block, but for both right and left sides. I don't want to have to re-input the info after flipping.

how's that?OK, I gotcha. I'll see what I can come up with if anything.

[jgratton]

This is frustrating. I have tried the internet options, even made AUGI an exception to pop-ups. I tried lowering my privacy settings. I used to attach all the time from work. Something with this laptop setup is different.OK I think this will work. I still have to keep clicking on manage attachments button several times and ignore the popup warning before it finally comes up.

[Chris.N]

OK I think this will work. I still have to keep clicking on manage attachments button several times and ignore the popup warning before it finally comes up.ok, maybe we can get a mod to split this into it's own thread. doesn't look like it fits with this thread title...

now that we see your block, can you clarify your question and issues?

[jgratton]

ok, maybe we can get a mod to split this into it's own thread. doesn't look like it fits with this thread title...

now that we see your block, can you clarify your question and issues?
OK sorry about morphing the thread. In a nutshell, I don't know how to move attributes/text while rotating geometry around the base point.

I have been using visibility states to their limit, but you can't copy attributes and make them invisible. You have to move them, but I want them to move automatically while the object is being rotated. I also want them to move when flipped.

I don't understand the steps necessary to get chaining to work properly.

[whdjr]

Did you read my post on the bottom of the fist page of this thread?

[jgratton]

Are you using Firefox or IE? I couldn't get mine to work in Firefox so if I attach a dwg I do it in IE.
IE 6

I'll just keep hitting the manage attachments button until it gives up and pops up.

[Chris.N]

OK sorry about morphing the thread. In a nutshell, I don't know how to move attributes/text while rotating geometry around the base point.

I have been using visibility states to their limit, but you can't copy attributes and make them invisible. You have to move them, but I want them to move automatically while the object is being rotated. I also want them to move when flipped.

I don't understand the steps necessary to get chaining to work properly.you don't chain text, you just include it in the action ,but make sure the 'lock location' option is checked. do a search for 'move, attributes, text' in this forum. this has been discussed a lot in here. Sorry, but i don't have the gift of linking searches like Mike does.

[jgratton]

Did you read my post on the bottom of the fist page of this thread?
Yes, I just need to get offline for a whil to try it! I'm not as quick as some.... Thanks, I will let you know how it goes...

[whdjr]

sort of. this would be my work-around untill flipping attributes also flips it's justification. left and right would only be shown individually. what it's for is an elevation marker for architectural elevations and sections. I want one block, but for both right and left sides. I don't want to have to re-input the info after flipping.

how's that?I got it to update one side from the other but both are still edittable so it is not user-proof.

[Chris.N]

I got it to update one side from the other but both are still edittable so it is not user-proof.care to post and provide explanation of procedure?

[whdjr]

care to post and provide explanation of procedure?.....UGH!!!!!.....

When I went to add my dwg file it cleared out my post I had already typed so this is a retype. I hope it is as good.


I used a block from the AutoCad tool palette with 2 atts on each end. I changed the values on one end so I could easily identify them when editting the other end. To edit the other I used 'DDATTE' and editted the 3rd attribute by replacing the value with a field that read the value from the 1st attribute, and so on for the 4th one.

Field-->Object-->select the block and then use the preview to find the value you need.

[Chris.N]

.....UGH!!!!!.....

When I went to add my dwg file it cleared out my post I had already typed so this is a retype. I hope it is as good.


I used a block from the AutoCad tool palette with 2 atts on each end. I changed the values on one end so I could easily identify them when editting the other end. To edit the other I used 'DDATTE' and editted the 3rd attribute by replacing the value with a field that read the value from the 1st attribute, and so on for the 4th one.

Field-->Object-->select the block and then use the preview to find the value you need.ok, but that method right there is why i need the 'master'

when you switch vis states and edit, you overwrite the field, and then it's game over....

[whdjr]

You're loosing me here with these vis states. What role do they play?

[whdjr]

Try this with vis states. Granted you shouldn't edit the attributes with the fields, but they still update whether they are visible or not.

[Chris.N]

You're loosing me here with these vis states. What role do they play?left vis has left justified text, right vis has right justified text. that's the only workaround i can think of till FLIP flips att justifications.

[jgratton]

If you want to move your text while rotating (but not rotate the text) then you need to set a point parameter for the text and include only the point parameter in the rotation action. Then you need a move action for the text to the point parameter. The point parameter needs to have the 'Chains' property set to Yes.

Does that help?
I tried just using the point parameters but the text moved to the wrong position. Then I tried using polar move. Same result.

What did Chris mean by locked locations? I can't find where to do this.

[Rico]

I tried just using the point parameters but the text moved to the wrong position. Then I tried using polar move. Same result.

What did Chris mean by locked locations? I can't find where to do this.
Here. Let's try this.

Because I don't exactly understand what you want, it's not perfect, but it's a good place to start .... is this close to what you were saying?

[Chris.N]

I tried just using the point parameters but the text moved to the wrong position. Then I tried using polar move. Same result.

What did Chris mean by locked locations? I can't find where to do this.to answer your Q, it is an option when you create your attributes located in the lower left of the attribute dialog box, or when you select an attribute, the option is found at the bottom of the properties palette. see attached.

[jgratton]

Here. Let's try this.

Because I don't exactly understand what you want, it's not perfect, but it's a good place to start .... is this close to what you were saying?Thanks for trying Rico. This hopefully explains the desired end result, 12 different possibilities of how it would look. I would also like the ability to use the large end as a basepoint too, but making a second db would suffice.

I will now try that lock option on the attribute like Chris suggested.

[Chris.N]

Thanks for trying Rico. This hopefully explains the desired end result, 12 different possibilities of how it would look. I would also like the ability to use the large end as a basepoint too, but making a second db would suffice.

I will now try that lock option on the attribute like Chris suggested.ok, for that arrangement, i'd suggest a parameter to adjust the text spacing with a point grip to manipulate it's location as a group. default placement should be where you think you'd use it most. if i get a chance, i'll see what i can do later, it's 5 now... ;)

[Chris.N]

hey Magic,

will this work for ya? at least with the text issue.... btw, i removed your 'vis' states and gave you a lookup for the bottom text.... whenever you change it, regen will be required.

[jgratton]

hey Magic,

will this work for ya? at least with the text issue.... btw, i removed your 'vis' states and gave you a lookup for the bottom text.... whenever you change it, regen will be required.
MAGIC! like that! The lookup is cool. I haven't figured out how to do that yet. I don't know how to change it between 3 states (fob/fot/blank) when the block is inserted into a dwg. The only visable grip is the insertion point, which is not on the reducer itself. That can be changed, but I was hoping for the attributes/text to move automatically to the left of the reducer when the reducer is rotated 90 degrees.

Thanks for taking the time to help, but I'm getting the feeling what I need cannot be done - at least not yet.

[H.Hunter]

I just did a block like this yesterday. Except I just skipped the flip and went with vis states to simplify things for me. The other problem was I wanted to be able to switch textstyles based on a lookup, but that isn't there yet. So I just made more vis states....blah. Comprimising... :evil:

[jgratton]

I just did a block like this yesterday. Except I just skipped the flip and went with vis states to simplify things for me. The other problem was I wanted to be able to switch textstyles based on a lookup, but that isn't there yet. So I just made more vis states....blah. Comprimising... :evil:
Yeah, thanks for sharing. I know what you mean by compromising. When I started this exercise, I figured once my reducer block was inserted, it would prompt me to key in the size (12x10 for example) I would then turn on one of 3 visibility states, concentric (no text), eccentric flat on top (FOT) or eccentric flat on bottom (FOB).

THEN I would use a rotate grip to rotate the reducer either 90, 180, 270 or back to 0. At 90 and 270 both the p-size attribute and BOB/FOT text would automaticall move to the side of the reducer, otherwise they would interfere with the flowline extending from either end of the reducer.

Finally a flip action could be used to determine which side of the flowline had the large end and which had the small end.

I definitely do not yet have the skills to pull this off, and either I am not communicating clearly enough or more likely this cannot yet be accomplished.

[megumby]

Hey,

I was woundering if you have solved this problem yet?
I have 4 visibility states with 2 attributes in each at different locations, and only want to type the informaiton in once and have it linked up with the other visibility states....
I've read all of this thread and I think that was sort of what you wanted to accomplish..
Did you end up getting it to work? If you could share it would be great.

[wroebuck]

Does this do what you want, as far as the original thread goes? If so I can explain the process.

[Capt. Computer Crasher]

From my understanding, attributes can only be edited with visibility on.

[Chris.N]

Does this do what you want, as far as the original thread goes? If so I can explain the process.
ok, have you noticed if it's the invisible attributes properties that make it unstable? or that it was created in 2007 or later? i tried crashing your block, and am unsuccessful! good work btw!

and i added stretch parameters to mimic my elev. tag blocks, and i STILL can't crash it. ~sigh~ looks like i'll have to rebuild mine...

[Chris.N]

From my understanding, attributes can only be edited with visibility on.
that's why you use an invisible attribute that 'feeds' the visibility dependant attributes thru fields. the invisible attribute is actually always there.

[mockdeep]

So how do you modify the invisible attribute? Is there a visibility state that shows it? Or do you modify it within the block editor? Either way sounds like about as much work as just changing the attributes manually. Maybe you would be better off making the left attribute the parent of the right, or vice versa, depending on which you use more often. This way, as long as you keep in mind which one to edit, both will be consistent.

[Chris.N]

So how do you modify the invisible attribute? Is there a visibility state that shows it? Or do you modify it within the block editor? Either way sounds like about as much work as just changing the attributes manually. Maybe you would be better off just making the left attribute the parent of the right, or vice versa, depending on which you use more often. This way, as long as you keep in mind which one to edit, both will be consistent.
first i need to ask if you opened up the file. the attribute is always "on", it's just that the attribute's PROPERTY is set to invisible.

and i've tried your suggestion, and the deal breaker is that you have to go back to the "parent" visibility state if you want to edit it properly to keep the fields in place. (one is always the parent, and the others will always be a slave. they can't be both)

either way, as with all fields, regens are necessary for update no matter with route taken.

[mockdeep]

Ah, I see. Sorry for the confusion, I'm still absorbing all of this DB stuff. I didn't see a successful implementation of this posted here, though. Is it somewhere else or am I just missing something?

Another question--what if you were to use a text object instead of an attribute for the child fields? I think this flips justification alright and you would be able to prevent users from ruining your field setup.

It's such a pain having to regen in order to update fields. Is there any hope that these might someday be separate?

[Chris.N]

Ah, I see. Sorry for the confusion, I'm still absorbing all of this DB stuff. I didn't see a successful implementation of this posted here, though. Is it somewhere else or am I just missing something?

Another question--what if you were to use a text object instead of an attribute for the child fields? I think this flips justification alright and you would be able to prevent users from ruining your field setup.

It's such a pain having to regen in order to update fields. Is there any hope that these might someday be separate?
ya know, i JUST got done with the 'attribute' vs. 'text' question in another thread and can't find it now! (otherwise i'd link to it)

the answer is no to the text, btw. it won't update. (outside of the Block Editor anyway) has to be attributes. I've placed DO NOT EDIT!! in the child attributes data prompt line in order to help avoid confusion.

not error proof, but as error resistant as i can make it at this time...

[Chris.N]

Another question--what if you were to use a text object instead of an attribute for the child fields? I think this flips justification alright and you would be able to prevent users from ruining your field setup.
Here's the discussion (http://forums.augi.com/showthread.php?t=70169)i referred to yesterday

[wroebuck]

I'm glad it worked. I use this method quite a bit.

[Chris.N]

I'm glad it worked. I use this method quite a bit.
what version ACAD did you create that in? is a vertical app involved?

[wroebuck]

That was created in 2008. But I have been using that method since the introduction of dynamic blocks. I construct the block geometry in the block editor. create my attributes. One parent that is hidden. then both of the child attributes on different vis states. I try to use the blockplaceholder field first & foremost. In this block it wasn't possible. So I link the fields to the parent. That way the user can just double click the block, edit the correct one & all is done.

[Chris.N]

That was created in 2008. But I have been using that method since the introduction of dynamic blocks. I construct the block geometry in the block editor. create my attributes. One parent that is hidden. then both of the child attributes on different vis states. I try to use the blockplaceholder field first & foremost. In this block it wasn't possible. So I link the fields to the parent. That way the user can just double click the block, edit the correct one & all is done.
hey, thanks!
i've only done one that's buggy, so i've never done another. I don't know if it's one of the other 'features' i've added that's wonky, or what. but otherwise, your narrative is the same for how i build such blocks.

maybe if i try from scratch it'll be fine.

[redbullsuzuki]

Howaya, sorry I'm late...
Can somebody post an example of a working dynamic block with fielded text linked to a master attribute in various visibility states...
I tried this with an existing block...
I got 2 pieces of text to take the value of a master invisible attribute, but when I copied it and revised the attribute, nothing happened... I went back to the first insert, changed the value and, of course, all the text is still linked to the first example of the attribute...
Grand, if everything has a common value... Nothing ever has common values, and then you have to remember where the original is, to make any kind of change... Not exactly convenient if someone else began the drawing...

Methinks that additional fields may be in order from the WishList :-) :-( ;-)...

[Chris.N]

Howaya, sorry I'm late...
Can somebody post an example of a working dynamic block with fielded text linked to a master attribute in various visibility states...
I tried this with an existing block...
I got 2 pieces of text to take the value of a master invisible attribute, but when I copied it and revised the attribute, nothing happened... I went back to the first insert, changed the value and, of course, all the text is still linked to the first example of the attribute...
Grand, if everything has a common value... Nothing ever has common values, and then you have to remember where the original is, to make any kind of change... Not exactly convenient if someone else began the drawing...

Methinks that additional fields may be in order from the WishList :-) :-( ;-)...
"text" or "attributes"

they need to be attributes.

wroebuck had the latest...

[redbullsuzuki]

Chris.N,
Text... When I tried attributes, they would not update...
I've tried something similar before for my attributed titleblocks...
I have an oversize attribute below the titleblock, outside of the plot area, which takes the drawing reference, via a LisP routine 'BigRef'... I tried field'ing this attribute to read the actual drawing reference on a constant basis... I can do so after insertion of the block but not in the DWG that is the titleblock... Not being an attribute, yet, and only an AttDef, I can't get the value out of it...

I gave up and opted for the after-the-fact LisP routine...

The same with the master invisible attribute, I had to edit after-the-fact of the insertion and every copy referred back to the original master attribute unless I editted them after copying... Kind of defeates the purpose ;-) ...

[Chris.N]

Chris.N,
Text... When I tried attributes, they would not update...
I've tried something similar before for my attributed titleblocks...
I have an oversize attribute below the titleblock, outside of the plot area, which takes the drawing reference, via a LisP routine 'BigRef'... I tried field'ing this attribute to read the actual drawing reference on a constant basis... I can do so after insertion of the block but not in the DWG that is the titleblock... Not being an attribute, yet, and only an AttDef, I can't get the value out of it...

I gave up and opted for the after-the-fact LisP routine...

The same with the master invisible attribute, I had to edit after-the-fact of the insertion and every copy referred back to the original master attribute unless I editted them after copying... Kind of defeates the purpose ;-) ...
always need to regen, save, plot, etc. (or whatever your field update settings are).. when using fields, period.

[dculver.42063]

What I would like to see is control of attribute’s justification, height, color, rotation within the lookup table.

[redbullsuzuki]

always need to regen, save, plot, etc. (or whatever your field update settings are).. when using fields, period.

All set, but no luck...
As I said, can someone post a working example...


What I would like to see is control of attribute’s justification, height, color, rotation within the lookup table.

If you can get the various justifications to work, the rest should be easy...
Unanticipated values can always be altered manually...

[Chris.N]

All set, but no luck...
As I said, can someone post a working example...



If you can get the various justifications to work, the rest should be easy...
Unanticipated values can always be altered manually...
~shrug~ if you want fielded "text" in a working BLOCK example, you won't find one, sorry. they only work (and update) with attributes all around.

post #43 in this thread is that example that uses a master attribute (to edit) with linked attributes (to show)

[redbullsuzuki]

~shrug~ if you want fielded "text" in a working BLOCK example, you won't find one, sorry. they only work (and update) with attributes all around.

post #43 in this thread is that example that uses a master attribute (to edit) with linked attributes (to show)

OK, would your experience of fielding to a master attribute include WBlock'ing the resultant block definition...
From a startpoint of the Sample.dwg/test block, I got additional attributes to work, not work, work again, but refuse to WBlock... Trying to insert the resultant DWG, the fielded links seem to have broken down...
Have you successfully WBlock'd a DB with functioning fields or do you just settle for nested blocks in a DWG, that become available for copying but not inserting...

Sorry, a recent PC crash has left me without the time to endlessly test all the ways of doing this and you guys seem to know your stuff ;-) ...

[Chris.N]

OK, would your experience of fielding to a master attribute include WBlock'ing the resultant block definition...
From a startpoint of the Sample.dwg/test block, I got additional attributes to work, not work, work again, but refuse to WBlock... Trying to insert the resultant DWG, the fielded links seem to have broken down...
Have you successfully WBlock'd a DB with functioning fields or do you just settle for nested blocks in a DWG, that become available for copying but not inserting...

Sorry, a recent PC crash has left me without the time to endlessly test all the ways of doing this and you guys seem to know your stuff ;-) ...
i guess i don't understand why you can't WBLOCK your DB out, and i've personally experience only minor bugs when placing those blocks into my Tool Palette.

one of the tricks (practices) i've discovered that's worked best, is to have all the master attributes in place BEFORE creating the linked Attributes, adn when creating the linked attributes, add the fields during the initial attribute creation.

never worked as well for me adding the fields after copying an existing attribute around.

oh, and you ARE making all of your attribute tags unique, right?

[redbullsuzuki]

i guess i don't understand why you can't WBLOCK your DB out, and i've personally experience only minor bugs when placing those blocks into my Tool Palette.

one of the tricks (practices) i've discovered that's worked best, is to have all the master attributes in place BEFORE creating the linked Attributes, adn when creating the linked attributes, add the fields during the initial attribute creation.

never worked as well for me adding the fields after copying an existing attribute around.

oh, and you ARE making all of your attribute tags unique, right?

All tags unique... Yes...
Master attribute first... Yes...
Tool pallette... Never, bring back tablets, I say...
WBlock... Not working, for this situation...
Nested working block, fixed after creation... Yes...

It just seems a bit too buggy for my liking... Albeit that we are waiting to be upgraded to AC'08 in work and I still use AC'06 at home, when I fix it... It's more annoying than anything, that it doesn't quite work the way you want it to, but I guess I can live with the workarounds...

[Chris.N]

All tags unique... Yes...
Master attribute first... Yes...
Tool pallette... Never, bring back tablets, I say...
WBlock... Not working, for this situation...
Nested working block, fixed after creation... Yes...

It just seems a bit too buggy for my liking... Albeit that we are waiting to be upgraded to AC'08 in work and I still use AC'06 at home, when I fix it... It's more annoying than anything, that it doesn't quite work the way you want it to, but I guess I can live with the workarounds...you have no idea what you are missing. TP's have allowed me to get rid of 98% of my clunky routines for office standards, and made standards compliance automatic.

[redbullsuzuki]

you have no idea what you are missing. TP's have allowed me to get rid of 98% of my clunky routines for office standards, and made standards compliance automatic???.

No speakee american...

Office standards??? Chance would be a fine thing...
I'm not a fan of anything that needs mice movement, I'm waiting for the development of an SID ; Synaptic Interface Device... Blink, and it's done ;-) ...

[Chris.N]

<snip>
Tool pallette... Never, bring back tablets, I say...
<snip>...


<snip>
I'm not a fan of anything that needs mice movement, <snip>...
you seem to contradict yourself.... :lol:

:beer: anyway!

[redbullsuzuki]

you seem to contradict yourself.... :lol:

:beer: anyway!

Tablet, not mouse... Old style digitiser...
Those were the days... ;-)...
Once the feel was acquired, they could be used almost blindfold, almost, certainly there was less looking around for that toolbar or pallette location... Symbols were wherever you had put them... If you had used one, you would remember the ease of use... I've just gotten sick of altering my style to fit whatever interface is in vogue this season... So, I abondoned using anything that I hadn't programmed into the least possible keystrokes... I learned commands, not toolbar buttons, etc....
I had a recent colleague who practically couldn't work after an upgrade, because the toolbars didn't have exactly the same icons... WTF...
:beer:... Momentary rage at the machine over...

[mbreeden]

So in all of your opinions, is having to regen or update fields better than retyping the information twice even if it is only 8 to 10 characters?

[Chris.N]

So in all of your opinions, is having to regen or update fields better than retyping the information twice even if it is only 8 to 10 characters?
In mine, doing that wouldn't be a biggie if only dealing with 1-2 blocks. However, when dealing with a column of 6+ blocks, globally flipping and not have to re-type the info is really nice.

[mbreeden]

from what i am experiencing, the only way to get this to work is to create the block, insert it into a blank drawing, edit the visible attributes to have the fields reference the block's invisible attributes, wblock, and now you are ready for insertation as a block, but upon insert it must be exploded.

Correct?

[Mlabell]

from what i am experiencing, the only way to get this to work is to create the block, insert it into a blank drawing, edit the visible attributes to have the fields reference the block's invisible attributes, wblock, and now you are ready for insertation as a block, but upon insert it must be exploded.

Correct?

No, to get this to work follow these steps.

1. Create your geometry for the DB.
2. Make your visibility states.
3. Add the invisible atts, and make sure they are visible in all visibility states.
4. Create your visibiliy specific atts. For the prompt place "do no edit", and for the value click on the field icon, and follow the attached picture.
5. Now everything should be all set! Close your block editor and you are ready to rock.:beer:
Clear as white mud?

[mbreeden]

when i was saying "create the block" those were the steps i was referring to.
The problem i saw in my block was that it couldnt read the value if it was referencing an attribute as the object type. Instead after inserting the block i would repath the "dont edit" fields to the block itself where i was able to pick which attribute i wanted to show there. This is why i would wblock it out because now it is reading the values in the block itself and not an attribute.
if you look at the picture you can see my field selection. Notice the object type is a block reference and NUM, NUMR, NUML, TAG, TAGR, and TAGL are my attributes.

Inst Tag.dwg is my working block. If you save it to your hard drive, insert it, and explode, it will work correctly.
If you can get it to work without having to explode, i will be surprised.

[Mlabell]

Inst Tag.dwg is my working block. If you save it to your hard drive, insert it, and explode, it will work correctly.
If you can get it to work without having to explode, i will be surprised.

Start be recreating all of the atts. If you copied them around that could be the culprit. Atts get real finicky with fields if they werent created as seperate instances. I recreated the atts and it seemed to work. Don't worry it only took all of us a few times to figure that one out. :banghead:

[mbreeden]

If you are getting it to work, I must be doing something wrong. Here it is with the new attributes. i have no idea where it is looking for the field but it aint my invisible attributes.

[Mlabell]

If you are getting it to work, I must be doing something wrong. Here it is with the new attributes. i have no idea where it is looking for the field but it aint my invisible attributes.

OOPS! I forgot to mention to change the atts that are driven by the invisibles to preset. Regen twice, then it should work...

[mbreeden]

It still dont work. I even went back and recreated the whole block again.

If you got it to work, can you post it so i can see it?
the only way i see it working is by having to explode it after referencing the block instead of the attribute def.

[Mlabell]

It still dont work. I even went back and recreated the whole block again.

If you got it to work, can you post it so i can see it?
the only way i see it working is by having to explode it after referencing the block instead of the attribute def.

If it doesnt work try attsync, from there I am not sure why it would not work on your machine.

[mbreeden]

i just dont understand it... yours works.

the only difference i see in the field expression is the objid...
mine: %<\AcObjProp Object(%<\_ObjId -1090296936>%,1).TextString>%
yours: %<\AcObjProp Object(%<\_ObjId -1090295376>%,1).TextString>%

why it dont for me just doesnt make sense. i am going to try this with some other blocks and see what happens... i will let you all know how it turns out.

[mbreeden]

ok... i mine has possibly always been working right, i think.
For some reason i have to change states and regen, or else the block will never update.
but once i change states, and regen it works like should, in both states.
I created a brand new block and it does the same thing; change states and regen for it to do anything.

personally it would make more sense to just explode it and then edit as needed.

[jl928563]

I just wrote this lisp routine to handle the regen of fields.

It will automatically regenerate all the fields in your drawings after you exit the DDATTE command. Nothing special, just thought I would throw it out there. We use the DA key command to start the routine, change it as you see fit.

(defun c:da () (command "ddatte" pause)(command "updatefield""all" ""))

Thanks for the very informative instructions for setting up attributes with multiple visibilities in dynamic blocks. Very helpful.

Jon