Announcement

Collapse
No announcement yet.

9357 label overspill

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    You might try setting the Message Box dialog font to something distinct like Comic Sans, restart BC3 to verify that it follows this setting, and then put it back to Tahoma. This exercise might be enough to convince your OS to provide the correct font when asked.
    Tim T Scooter Software

    Comment


    • #17
      > You might try setting the Message Box dialog font to something distinct like Comic Sans,
      > restart BC3 to verify that it follows this setting, and then put it back to Tahoma.

      Done... and the problem disappears.

      > This exercise might be enough to convince your OS to provide the correct font when asked.

      It was apparently enough to convince your BC to provide the correct font when asked.

      Comment


      • #18
        > It was apparently enough to convince your BC to provide the correct font when asked.

        No, BC did nothing different after you made that change. It asks the OS for the standard GUI font and uses what is given. I tried BC3 on 3 XP systems here and they all show Tahoma. I don't know why your system provided the wrong font.
        Tim T Scooter Software

        Comment


        • #19
          > No, BC did nothing different after you made that change.

          It delivered a different font.

          Comment


          • #20
            As Tim correctly described it, BC does not deliver fonts. It tells the OS what font to use (in this case, the Message Box font) and the OS "delivers" the font.

            Although we may never know for sure what happened on your system, the most common cause of such font issues is usually a missing or corrupt .ttf file on your system. When Windows cannot locate a font in the exact language/codepage that was originally defined, it substitutes a similar font. This can cause display issues as Windows uses the specifications from the original font (width of characters, etc.) while displaying an alternate font that may differ slightly from the original. Changing the font will usually correct the problem. Since the OS will only provide a list of the fonts that it knows to be valid on the system, reassigning a known font implements it correctly and eliminates the font substitution.

            Most likely the Message Box font defined on your system was not Tahoma. One possibility is that the Message Box font may have been altered sometime in the past when a Theme was applied to your system. Whatever the case, the defined font could not be found, so the Display settings defaulted to Tahoma while delivering font specifications for a font definition that it could not resolve.

            I am sure that the Scooter team will not be interested in dragging out an argument on this topic, but the fact is that your OS, for whatever reason, was performing a font substitution. Changing away from and back to Tahoma allowed the OS to correctly implement the Tahoma font on your system rather than to substitute a font for whatever was not working correctly before.

            Originally posted by Tim View Post
            I see your system's dialog font is different than chrroe's or mine. We'll try to improve this in a future release.
            In my professional opinion, Tim's original assessment was correct. He said that the Scooter Team would work to improve the handling of alternate Message Box fonts in a future release. Other than that, this was an OS font substitution issue, not an issue with BC3 displaying the incorrect font. A reason you may have noticed the issue in BC3 and not in other software is that BC3 allows buttons to be resized to minimum width eliminating the extra margin space on the button face that other products typically preserve.
            BC v4.0.7 build 19761
            ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ

            Comment

            Working...
            X