Layer overrides in XREF does not effect attributes - I need it to

[Anonymous]

We have a new amazing multileader that uses a block with attributes to label our drawings. The attributes are found in the key (callout) of the block, and the name of the item I'm labelling. In my site plan, I want to show the name of the item, but not the key. Before we developed this great multileader, we were just using mtext to name the items.

ATTMODE cannot = 0 because there are some attributes I need to see.

ATTDISP doesn't help either

No amount of layer override (freezing, turning off, setting colour to 255,255,255, setting to not plotable) is working!

The stuff I want to turn off, the key/callout, is on it's own layer - so turning it off should be easy! Other items on the layer are turning off and functioning fine normally.

It seems like attributes in xrefs are completely uneffected by layer management! In the base drawing, the attributes behave in the expected way with layer management.

[wispoxy]

It better not effect it. Attribute Definitions / Fields have their own settings and font type.

[qnologi]

Could you post a .dwg with only this "amazing multileader"? That way someone could have a look see at what you need help with.

Or maybe a screenshot.

TLQ

[john.vellek]

HI @Anonymous,

Pleae attach a sample drawing that contains your new multileader. Then, please explain what you are trying override so I can see if it is possible.

I look foward to assisting you.

[Anonymous]

Attached is a simple version of our amazing mleader. The attributes inside the block - inside the mleader seem to take on the properties of the mleader. You'll see in the attached file that the mleader is doing what I've just described, and the block is functioning as expected. I need to be able the freeze the numbers and the geometry, while keeping the text and the leader on.

Hope that helps and thank you!

[john.vellek]

Hi rachelGEQA9,

The way your leader is currently working is as designed. Unfortunately, the text attributes are going to behave like the multileader itself even though they are defined to be on their own layer.

A workaround might be to keep the tag separate from the leader. create your leader, insert your tag block, and then group them.

Please hit the Accept as Solution button if my post fully solves your issue or answers your question.

[Anonymous]

Thanks for the answer and suggestion. I was really hoping for something a bit easier.. We had an issue with the separate items before if we had to modify the leaders. I think the group may create the same issues we were having before when we modify. Grouping would work nicely if the angle of the leader would never have to change. 

While brainstorming ideas in the office, we considered creating a solid hatch with colour 255,255,255 on a layer that can be frozen or unfrozen to hide/reveal the text beneath. Just tested that one... It doesn't work either!! The attributes don't hold the drawing order!

[elshawadfy · Accepted solution]

Hi @Anonymous,

I created an multileader as you asked, (although the attribute dosn't take after the layer it's inseted in, when you turn the layer Att_Txt of only the attribute is turned off)

What you need is: to make sure the attribue is on it's own layer, it's color is set to by layer not by block, in the Mleader style: the block is set to bylayer not byblock..

The file is attatched.. 

[elshawadfy]

The file I attatched was usng one attribute that can be turned off separately..

Unfourtinately when using more than one attribute they all follow the last one's layer..

My workarround woul be: if you want to turn off some atriibutes only, use Battman and make it invisible, sync and regen after exitting..

If you want it back on, same thing..

[Anonymous]

Thanks for looking into this! Maybe we're just labelling in a strange way. We have component key plans, surface key plans, and site plans. I want the entire mleader to appear in the component and surface key plans, but only the leader and the component name to appear in the site plan. We label in the component/surface key plan model space, then xref that into the site plan.

Thank you again.