Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
I first tried to find something about this already on the forums, but my searches came up with nothing, so I will present it.
As probably everyone here knows, text can be added to a dimension by going into its properties. For the longest time, in all the Pro/E versions I've used up through Wildfire 2, the dimension line has always automatically moved to make room for this additional text after it has been typed in. However, I noticed that when we moved up to Wildfire 5, the dimension lines no longer make room for any added dimension text. There is room for the actual dimension value itself, but not for the extra text, and the dimension line cuts right through it, which looks awful. See my attached image for visual reference. On the left are screen captures from Wildfire 2, and on the right, from Wildfire 5 (or Creo, which is what we have now). To be precise, what we are using now is Creo Elements/Pro 5.0, build M090.
I do not like this. I want it to work like it did in WF2 and before. Is there a fix? Could it be as simple as a setting in the drawing options file or config file? Using "break" to manually trim the line is not convenient, should not be necessary, and has to be re-done for any additional changes to the text or moving the dimension.
Advanced thanks to anyone who can offer a solution.
Solved! Go to Solution.
It looks like the following article addresses this issue.
https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS118875
Mark,
I tested your problem in Creo Elements/Pro 5.0, build M120. Vertical linear dimensions are displayed correctly, radial dimensions incorrectly. I think you have to report the problem to PTC Support.
Martin Hanak
Out of curiosity, has this issue been resolved?
currently having this issue
oops... currently in Creo 2.0
Yes, see Clint's reply below. Not sure which build you have; the fix was implemented in Creo 2.0 M070. I tried it and it works.
It looks like the following article addresses this issue.
https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS118875
Thank you, Clint, for posting this solution.