LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Front panel resolutions: Application vs. VI mode...

This is probably a silly question but it caught me by surprise as I don't recall seeing this in any of the old versions of LabVIEW. When I run a LabVIEW program in the normal (VI/debug) mode the front panel resolution is very high and the fonts are smooth as if they are post script/vector graphics. But as soon as I compile the code to an application in the application builder the front panel/fonts become pixelated... as if it was a lower resolution bitmap. Below are two images, one from a normal VI (left) and the other (right) after it has been built into an application. What setting do I need to set to have the built/compiled application retain the same resolution as it has during normal (VI) mode? I am using LabVIEW 2021. Thanks! (If both images don't show it might be due to a temporary server problem. Not sure but the question should be clear even without the images)

VI.png

 

App.png

0 Kudos
Message 1 of 5
(1,161 Views)

LabVIEW doesn't always play nice with Windows resolution scaling. Is your monitor scaling set to 100%?

0 Kudos
Message 2 of 5
(1,128 Views)

For this project I am using a Mac (mini) actually and the display setting in MacOS is set to the default of the display. Perhaps this issue is a Mac only issue? It is just strange that things changes just because I compile the code. I would expect that What-You-See-Is-What-You-Get... before/after compilation. Not a big deal but if there is a simple solution/setting I am all ears. Thanks!!

0 Kudos
Message 3 of 5
(1,109 Views)

Your computer likely sees the LabVIEW dev environment as a different application entirely from your created executable (which it is). It may apply different scaling settings to them, or even render one with a different graphics card than another. Unfortunately I'm a Windows guy, but I suspect this has to do with your computer, not your LabVIEW code. Hopefully someone with some Mac experience can help.

0 Kudos
Message 4 of 5
(1,105 Views)

Thanks. That makes sense. Seems like a LabVIEW bug on MacOS if there is no way around it with a setting. For comparisons I just tried LabVIEW 15 on Windows 10 and it does not have this problem with compiled applications and I also never recall ever having this problem in the past with LabVIEW on Windows. I have not used LabVIEW on Mac's since the mid 90s so I can't say if this is a new issue or not. Anyway, if any Mac users are on here and know how to fix this, please let us know. Thanks!

0 Kudos
Message 5 of 5
(1,071 Views)