Font resizing on target machine

[cgibson]

Hi Folks,

I am here with another font born tale of whoa.

I am developing a LabVIEW application in LabVIEW 2017 on a Windows 7 box. The application target is a panel PC running Windows 10. 

The GUI has been designed by a UI/UX developer who specified the Roboto Flex font. So, the GUI is in Roboto Flex although there are a number of different sizes depending on the GUI element. 

When I open this on the Windows 10 panel PC, the size of some of the elements are bigger than they are in the development machine. I can tell this in some cases because they overrun the buttons they are boolean text for. 

I checked the Windows font scaling in the dev machine and the target. Both are 100%.

The font has been installed on the target. 

As a test, I used a property node to show me the boolean text font and font size on one of my errant buttons and then ran this on the target. It reported the correct font and the correct size when run on the target machine. 

I know that some people solve font problems by setting the default fonts and sizes in the LabVIEW.ini file, or the application.ini file for an .EXE. I don't think this applies to me since I have set the font on the GUI to use Roboto Flex for all the controls. (Although the Font size differs.)

Any suggestions for other settings to check, or how I might get the text to render at the same size on both machines?

[ZYOng]

Running Executables or Installers on Different Windows Versions

Installers and executables are only guaranteed to work on the operating system they are built on.  For example, a Windows 10 installer or executable may not work as expected on a different Windows version (e.g. Windows XP, Windows 8, or Windows 7).

You should build your exe on a Windows 10 machine.

[Yamaeda]

Check Windows Scaling, Compatibility mode, DPI and such.

[aeastet]

I would also make sure the font you are using is available on the Windows 10 computer. Even if the font you are using is there sometimes there are different versions. If the font is not on that computer it will default to a default font and that may be why you are seeing the difference.

[altenbach]

You might want to double-check that there are no symbolic fonts hidden somewhere. For example if you just place a modern control on the front panel and select it, the font will show as the configured non-symbolic font. However, it turns out this is only true for the label/caption.. Once you click inside the control to edit the value, the font suddenly shows as "Application Font" for no good reason at all. (For system controls, it will show as "dialog Font" to add to the confusion).

Only after selecting the control and set the font in the dialog, also the numeric field will be non-symbolic. Finally!!!!

Suffice to say, this has annoyed me for decades and Darren modified the VI analyzer test to check for this.

There is now a VI analyzer test that you can configure to check that only non-symbolic fonts are allowed. This is the ONLY test I always do before building an application.