Skip to main content
B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
November 16, 2016
Solved

Reference Balloon font

  • November 16, 2016
  • 5 replies
  • 3840 views

We have changed our default font from Font to Isofont on our drawings. We can select and update the font on most items, including balloons for the BOM. However, we cannot find a method to change the font for a reference balloon. Is this an oversight on the part of PTC software designers, an undocumented feature (bug) or actually by design? If by design, then I will open an enhancement request for Creo 22 (not a typo, I figure PTC will take that long to fix it) and hope that others agree this should be fixed.

Best answer by mender

I think that an SPR would be better than an enhancement request here.  There might be some inobvious background, but it certainly sounds odd.  I'll keep an eye out for the SPR and investigate the issue.

5 replies

S
23-Emerald III
StephenW23-Emerald III
23-Emerald III
November 16, 2016

THAT REFERENCE BALLOON!!! ARRRGGGGHHHH!!!

It has been my experience that once a reference balloon has been added to a drawing you can never ever update it.

I really would like someone to prove me wrong. I've applied every hack I could to figure out with no luck.

M
mender12-AmethystAnswer
12-Amethyst
November 16, 2016

I think that an SPR would be better than an enhancement request here.  There might be some inobvious background, but it certainly sounds odd.  I'll keep an eye out for the SPR and investigate the issue.

    D
    dschenken1-Visitor
    1-Visitor
    November 16, 2016

    It won't be Creo 22. PTC has never gone above Revision 20** without changing the product name. Mathcad only made it to15 before becoming Mathcad Prime.Pro/E got to 20. WF made it to 5.

    ** They broke it to 2000i and some other version names, but the string of sequential numbers ended at 20.

    B
    23-Emerald III
    BenLoosli23-Emerald IIIAuthor
    23-Emerald III
    November 16, 2016

    What is in a name anyway? Internally, Creo3 is version 34 according to the LM files. I may have been better off saying PTC/CAD Parametric software version 52!

    I did beta testing on Unigraphics V19 one year. About half way through the beta test distributions the name changed from Unigraphics V19 to UG NX1.

    Is it Friday yet, I think I need the 3 day week next week sooner.

      B
      23-Emerald III
      BenLoosli23-Emerald IIIAuthor
      23-Emerald III
      November 16, 2016

      Case 13371450 has been opened.

      S
      23-Emerald III
      StephenW23-Emerald III
      23-Emerald III
      November 16, 2016

      If you don't mind Ben / Matthew, post any kind of resolution you come to. I'm very interested in this since it touches on issues I have had with reference balloons.

      R
      RaphaelCNascime1-Visitor
      1-Visitor
      February 20, 2017

      I just wanted to post an update to this issue.

      We've looked at the SPR and it turns out that this isn't a bug per se. The reference balloon is based on a drawing symbol and drawing symbols in general do not provide the capability of changing the font for an individual instance on the drawing - you have to edit the symbol definition to change the font.

      That being said, the best way to fix this would be to add support to symbols in general for changing the font of an instance. I've added this enhancement to our backlog of things to be considered in the future.

      In the meantime, there is a workaround that could be used to edit the default ref balloon symbol definition to use a different font. You can find a description of this workaround here: https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS23593

      I would just issue a word of warning that you should be careful when editing the default symbol found in the Creo loadpoint and take a copy of the unedited one before making any changes so you can revert it when needed. Also, since this item is in the Creo loadpoint you'll want to take care when updating the software as it might be overwritten.

      Terms & ConditionsCookie settingsAccessibility statement