07-19-2023 04:48 PM
This VI works fine in the IDE, but not in an executable.
Any suggestions would be appreciated (other than the obvious of manually copying the font specs from labview.ini to a custom app.ini).
07-20-2023 01:34 AM
What does not work fine in an executable?
I created an executable (Application.exe) of your VI.
- if the entry 'appFont="Arial" 12' is in Application.ini the executable returns 'Arial' and '12'
- if appFont is not in Application.ini the executable returns an error 1520.
What do you want to achieve with your VI?
07-20-2023 09:32 AM
@UliB wrote:
What does not work fine in an executable?
I created an executable (Application.exe) of your VI.
- if the entry 'appFont="Arial" 12' is in Application.ini the executable returns 'Arial' and '12'
- if appFont is not in Application.ini the executable returns an error 1520.
What do you want to achieve with your VI?
I want it to work without having to manually copying the font specs from labview.ini to a custom app.ini.
07-20-2023 11:13 AM
@paul_a_cardinale wrote:
@UliB wrote:
What does not work fine in an executable?
I created an executable (Application.exe) of your VI.
- if the entry 'appFont="Arial" 12' is in Application.ini the executable returns 'Arial' and '12'
- if appFont is not in Application.ini the executable returns an error 1520.
What do you want to achieve with your VI?
I want it to work without having to manually copying the font specs from labview.ini to a custom app.ini.
So do I.
I gave up years ago...
07-20-2023 12:31 PM - edited 07-21-2023 12:50 AM
There is a vi analyzer test to find all symbolic fonts. Replace each with a defined font. (Discussion leading to it).
07-20-2023 12:45 PM
@altenbach wrote:
There is a vi analyzer test to find all symbolic fonts. Replace each with a defined font.
My use case was to parse a picture control string, to render it in a PDF.
However, "Application Font" doesn't mean anything if you don't know what the "Application Font" is.
And there is no way to query that.