LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Font size/appearance problem on Windows 7 executable

Solved!
Go to solution

I'm no Windows 10 user, so I can just give some hints, but I try to answer the questions as good I can.

1.) On a remote front panel either You use LabView to run the FP-code, then the LabView.ini on Your system will set the defaults, otherwise if You use a compiled version of your_fp_code.exe, then You will have a your_fp_code.ini, which set's the fonts. For completeness: if the fonts are not set in the .ini, then a default value will be used.

 

2.) The keys in the .ini-file, given in former posts of this thread have only an influence to the Application-, System-, and Dialog-font. So, if You set another font, it will be hardcoded and won't adapt to the target system. This might be a problem, if the chosen font is not installed on the target system, e.g. Segoe UI on Windows XP - then a default font will appear instead.

 

3.) Here I can't give a proper answer, it will deepend on Your use case. As a side note, I experienced, the font-size, given in the .ini-file, doesn't override the font-size used in the UI. May be, it is used only to override the default font size. Since Windows 10 uses still Segoe UI as Windows 7 does. My guess is, the UI elements become smaller and the font size stays the same, because it is manually changed to 15pt.

 

4.) "Project Explorer->Tools->Options...->Environment->Fonts" just sets the according keys in the .ini file, so it's the same effect.

 

0 Kudos
Message 21 of 22
(921 Views)

further to this embedded fonts for website has also been around for ages.  Currently a typical LabVIEW application requires so much additional installers that it is embarrassing to not include the font support that would be less than a few megs for any given OS.  My issue is not so much the revision of windows as the localized version in a given country.  The best  solution would be to embed the fonts such that they are immune to windows settings and can be distributed regardless of Windows version both location and revision related.  Add this to the next version and I would buy it for that reason alone.  Otherwise to me it is not worth it.

0 Kudos
Message 22 of 22
(896 Views)