Text height bug/issue with Styles & Child views

[llorden4]

I've got an issue with my Style rules not being complied with with children views (none-base views).  I'm required to use a non-standard height for all my text, so please let's avoid the conversation over why I'm not using the industry standard of 1/8" text height.

The goal here is to have my view annotation to have a text height of 0.1 in tall.  When placing the Base View, the rule is followed correctly, however any view created from that view afterwards (projected, section, detail) has the text come in at a height of 0.125 in.  There's not a single text rule in my set that has a height value of 0.125 assigned to it so I have no idea where this text height rule of 0.125 in is coming from.

I know this issue goes back to at least 2016 and continues to be a problem with 2018, I have not as yet loaded 2019 to test.  Maybe I'm overlooking something, I'm looking for some assistance to point out what I'm overlooking or some confirmation that there's a bug in the software.  Attached are some screenshots of the styles in use as well as a blank template file with the styles loaded for your review.

[JamieVJohnson2 · Accepted solution]

Found it.

Style and Standard Editor \ Standard \ Sabre Standard \ View Preferences \ View Label Defaults \ View Type (drop down box), Display, use Edit button.  This is where they are overriding what you set using the text standard.

[llorden4]

Great find, that was hidden well.

I'm finding I'm not able to change these values and permanently save them to my template.  I can edit them and change the values, but I don't get any options to Save to Style Library once I get the values set as desired.

[JamieVJohnson2]

Styles in a template can also be managed (aka overwritten) by styles in the style library (Inventor Options \ Files \ Design Data).  The styles in your template must be synchronized to the design data or it will overwrite any file opened or created that uses that design data per your project (.ipj) file settings.  The files in the Design Data folder must not be read-only (for us we check the entire set into Vault to keep from tampering), then use the Manage \ Styles \ Save command to Push to the Design Data and Manage \ Style \ Update command to Pull from the Design Data.

A good methodology here is this:

1.  Check out Design Data files (make sure all files are read-write for current user).

2.  Update styles to match template file to Design Data.

3.  Modify Styles in template file, and save template file.

4.  Save template styles back to Design Data.

5.  Lock down Design Data Files (set all files to read-only, or copy to vault or simply make a zip file for backup).

[llorden4]

Dangit, I knew that...   rookie moment!   Thanks!