Move an attribute with visibility states

[Ed Jobe]

I've searched this forum and can't seem to find what I'm looking for. I'm working on a db of a wire tag that has six positions (see attached). Right now it has six atts, and only one gets filled in upon inserttion. I just want one to move with each vis state, or is there a better way?

[Chris.N]

I've searched this forum and can't seem to find what I'm looking for. I'm working on a db of a wire tag that has six positions (see attached). Right now it has six atts, and only one gets filled in upon inserttion. I just want one to move with each vis state, or is there a better way?

hmmmm, short of getting it down to one attribute somehow using a lookup, i can already see it being down to no less than 2 states using flips anyway, but only if you don't mind a middle justified attribute.

1 state for middle ones, the other for offset (each corner)

what do you think?

oh, and how tagged, what kind of text is used? (fishing for length issues)

also, (and i'm sure you're still in the middle of developement and haven't gotten that far...) you'll need to make each tag unique in the DB regardless of visibility...

[Ed Jobe]

No more than 15 chars, but usually 3-6.

Would it work to have one invisible attribute, and then 6 fields for each location?

[Chris.N]

No more than 15 chars, but usually 3-6.

Would it work to have one invisible attribute, and then 6 fields for each location?

i've done that, and it makes for a REALLY finicky block. as soon as somebody copy/pastes one of those blocks (at least in our office), it's nuthin but "######" signs everywhere!

[Ed Jobe]

i've done that, and it makes for a REALLY finicky block. as soon as somebody copy/pastes one of those blocks (at least in our office), it's nuthin but "######" signs everywhere!

The attached seems to work, but the fields won't update after I change the attribute value.

[Chris.N]

The attached seems to work, but the fields won't update after I change the attribute value.

even after regens?

fieldeval set to 31?

ok, just looked and everything should be an attribute. have you had this setup work for you in the past?

you can't have the 'child' attributes set to constant either for some reason, so i always put in the prompt field for the attributes DO NOT EDIT THIS LINE!!

it seems to work for those that can read...

[Ed Jobe]

Si, Si, senor. However, it will while in the block editor, just not after its inserted.

[Ed Jobe]

I have a wishlist item that's been approved. Be sure to vote for this one.

[Ammon]

Thanks for the info. I will definitely be voting for that one.

[BrenBren]

Thanks for the info. I will definitely be voting for that one.

~insert shameless plug~

You've only got until Monday to vote!!