child style component

[CADmgrMike]

I have some structure labels that have parent/child relationships.

I have revised the parent so one component isn't needed. I can delete the component in the parent, but it's still showing up in the child style even though it's not being used.

Any ideas how to delete it, or am I missing something?

[stevenh0616]

Hey Mike,

I tested here in 2018 - made a child, deleted a component, and it worked in my drawing. The child style is not in use correct? What version are you on? Your signature says 2016 SP2 - but I know there's SP4 out for 2016... You have all updates?

Maybe you can share your drawing and I can look

[CADmgrMike]

I'm using 2019, but the style was created in 2017. I know the component isn't being used or it wouldn't let me delete it in the parent.

I'm working on a drawing to post.

[stevenh0616]

Thanks Mike. I tested in 2019 as well and it seems to work here. Here's what I did...

- Created a structure label child style

- Changed the layer of the child style

- Opened the parent style and removed a component

- Opened the child style and confirmed component was removed

- Right clicked on child style and deleted.

I guess I'd need to see your drawing to see what's happening.

Or you could post a screencast.

[CADmgrMike]

I attached a drawing. I have a parent style with two child styles.

I delete a component in the parent style, but it still shows up in the child style.

I can't delete it.

[stevenh0616]

Hey Mike,

I opened your file and can see the issue on my end. However, when I test the same issue here, it works. I've added additional components to the parent and they show up. I've made them blank (no text), and have tried editing the label text and made sure they were in use - it still works here.

I'll do some tests in making the style 2017 and up to 2019 to see if it's something there I can replicate. In the meantime, can you confirm you have all the same updates I do?

[CADmgrMike]

Right now, I'm still updating styles in 2017. Here are the versions I'm running:

[stevenh0616]

It's definitely an odd issue. Does it happen for every component you add? Are you adding them in 2017 and then opening and saving in 2019 when it happens? I've only tested within 2018 and 2019

[CADmgrMike]

I have not tried it yet in 2018 or 2019. Still working in 2017.

I have not  tried adding a new component and then deleting. I only came across this because I wanted to revise some of our existing labels and remove a component. That's when I found out it wasn't deleting in the child style.

I guess I could migrate these to 2019 and see if the issue persists.

[CADmgrMike · Accepted solution]

Update:

I figured out after deleting the component in the parent style, I needed to close the drawing and reopen.

Then I could delete that component from the child style.

Thanks everyone for the help.

[Anonymous]

I have a similar issue. I have style that where created under the Standard label Style. I am trying to make my tags go into designated separate layers that I have assigned in the tag style individually but they keep going into the one associated with the parent which is Standard. 

Can anyone help?

[rl_jackson]

This is happening just as instructed. The parent it the ROOT, it controls everything just as in life a parent controls... Exit from the controlling factors and you gain additional control, assuming there are no additional ambient settings .

[Anonymous]

How do I exit from the controlling factors of the parent to gain control of my child tag label line and bearing styles?

[rl_jackson]

I generally don't create a lot of child styles. Ones that I do our for things like adding that the Bearing & Distance is a Deed or Plat call or both.

I generally create a new parent and have multiple parents that I will add child styles too. Just seems to make the world go round a little easier.

So in your case I would have a Boundary Label Style, a Boundary Minor Label Style, and I don't create tag styles, since those are already built into the labels. I always label the Bearing and Distance first then run around the site and create the Tag labels from them in the order that I like this avoids the glitch of C3D skipping tag #'s.