LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
Showing results for 
Search instead for 
Did you mean: 

Font size standardization

Once in a while I complain about font issues in general (here, here, or here), but one of the really weird things are the font sizes as used in LabVIEW.


The font dialog lists them as units of pt, but for some reason they are quite different in size from the same sizes in any other applications (browser, word, etc.). LabVIEW also shows other problems, for example tahoma 14, 15 all look exactly the same... why??


Here is a side-by-side comparison of a wordpad document and a LabVIEW panel. Each line is configured for the indicated font size.


As you can easily see, LabVIEW is the exception. Any other applications I tried agrees with the left panel.


Idea -->LabVIEW should also standardize here!




  • UI & Usability
Member fr@nk

Please, please please do something about the font situation. Fonts need to translate transparently from development to deployment environment.

I'm working on a program and the FP looks fine on my 24" monitor running in Labview. I build an executable and run it on the same computer and the fonts are wrong - overlapping, hidden, affecting control size, etc.

I found thread on the Labview discussion forum where GerdW mentions that some keys need to added to the executable's INI file for a Windows 7 app.

The example shown was: 

    FPFont="Tahoma" 13

    BDFont="Tahoms" 13

    appFont="Tahoma" 13

    dialogFont="Tahoma" 13

    systemFont="Tahoma" 13

I tried this with the last 3 entries and had some success but now some other, much larger text had been modified . I right clicked the new problem text on the FP in Labview and there is no indication what the current font settings are. I can blindly change them but don't know what I'm changing from. As the FP looks OK in Labview I'd have to build every project and run it, then go back to Labview and try blindly screwing it up so it would look OK when built.

Also, the INI file is regenerated on each build so I either have to figure out how to make and include a template file in the build that will add the required font information but not mess up anything else.

All of this doesn't include moving from one monitor size to another or from one version of Windows to another, which doesn't seem to be a problem.  


Member adam5532

Large Font support is currently poor in LabVIEW compiled executables. In Windows 7, if you set Control Panel>Appearance and Personalization>Display to 125% or 150%, on some computers button text will overrun the buttons, and labels will run into other things. From what I can tell so far, it seems to depend on the video card/driver. What seems to happen is that all windows, buttons, and fonts get scaled up, and then with some graphics drivers, the fonts also get enlarged. So, the fonts get enlarged twice and then are too big. If a user were to modify the individual Windows UI fonts in Control Panel>Appearance and Personalization>Window Color and Appearance>Advanced (if they can find this in its new illogical location), it might work OK (haven't tried it), but a user is much more likely to just alter the Display size.


The only apparent work-around is to add a text size property for EVERY control, indicator, and label in your UI, which will lock down the text size so it isn't scaled by Windows (per the LabVIEW KB article "Why Does the Font Size Change When Running a LabVIEW Executable in Windows?"). We just did this for a distributed application and it took hours and required over one hundred property nodes to be added.


This isn't exactly the same as the issues discussed previously in this Idea, but it seems that it is all related to revamping the font engine, so if/when that is done, this problem should be addressed and resolved as part of it.

Trusted Enthusiast
Trusted Enthusiast
Status changed to: In Development