Fonts not correct after installing LabView on new computer

[Terje]

I have just received a new computer and installed LabView 2010 (same version as on my old computer).

On the new computer, it seams as all fonts, on the front panels and on the block diagrams, are too big. See attached images of the same VI opened on the two computers. My old computer runs Windows XP and the new computer Windows 7.

What could it be? It would be a lot of work for me to manually correct the fonts.

[altenbach]

read e.g. this.

Seems the link there is broken, It should point to this document. I see if I can get it corrected.

[Terje]

Thanks altenbach for you answer

This seems to be more than just a porting issue. It seems to be problems with the font in the development environment itself as well. The application attached in my previous post is an example delivered together with LabView. Do other Windows 7 users experience the same behavior?

[altenbach · Accepted solution]

If you don't define a specific font for your panel, the "application font" used by LabVIEW is whatever is set for the windows theme.

Obviously, the two machines differ here.

I agree that fonts are one of the weak points of LabVIEW, so if you feel the same way, vote for a few related ideas:

• Persistent font Settings
• A better way to specify (default) fonts

[Terje]

Thanks altenbach, you pointed me to the solution.

If anyone else experience this issue, it is solved by changing the font size in Windows

[RavensFan]

Not just font size comes into play here, but also the system font is different on an XP vs. a Vista or Win7 computer.

Take a look at this link.

[Coq_Rouge]

How Labview handle fonts is very awkward and clumsy. It is really annoying. I have tried to get some answers from NI why they have done it this way. I have contacted NI support about this. But all I get is some automated answers how to get around this problem. Thanks but I already knew that. It would be nice if someone from NI could comment on why they do not bother to do anything about this. As it has been a problem dating back to the windows 3.11 days.