LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Text Rendering in LabVIEW

Sorry, I should have tested the AI generated file first before posting it. I used the one below last night.

 

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <!-- Step 1: Force the app to look DPI Unaware so Windows steps in -->
      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</dpiAware>
      <dpiAwareness xmlns="http://microsoft.com">unaware</dpiAwareness>
      
      <!-- Step 2: Instruct Windows to apply enhanced GDI vector scaling -->
      <gdiScaling xmlns="http://microsoft.com">true</gdiScaling>
    </windowsSettings>
  </application>
</assembly>

 It did work for my application. 

0 Kudos
Message 21 of 25
(427 Views)

These manifest files work in that the app builds and runs, but they are not doing exactly what the Compatibility setting does for the appearance of the text. 

 

0 Kudos
Message 22 of 25
(410 Views)

@FlatCat wrote:

Yes! This one and the one from thols seem to be working. The app builds, runs properly, and the text looks better. 

 

i just hope it's ok to delete the many tags in the default manifest that LV makes. 

 

Thanks so much to everyone. 


I think those other tags may be important if you want to run as admin, if there is a specific version of a library you want to use, or enforcing Windows version requirements. Otherwise, it probably just uses the defaults which are okay for 90% of the things.

 

Don't know if you can download it or it is part of VIsual Studio, but Mage.exe and MageUI.exe allow you to modify, create manifest files

0 Kudos
Message 23 of 25
(403 Views)

@mcduff wrote:

Sorry, I should have tested the AI generated file first before posting it. I used the one below last night.

 

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
      <!-- Step 1: Force the app to look DPI Unaware so Windows steps in -->
      <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">false</dpiAware>
      <dpiAwareness xmlns="http://microsoft.com">unaware</dpiAwareness>
      
      <!-- Step 2: Instruct Windows to apply enhanced GDI vector scaling -->
      <gdiScaling xmlns="http://microsoft.com">true</gdiScaling>
    </windowsSettings>
  </application>
</assembly>

 It did work for my application. 


Yes, it is clear visual difference when enabled or not:

2026-10-12_231110.png

Message 24 of 25
(388 Views)

on the other hand you must be extremely careful with gdiScaling, because of this:

Screenshot 2026-10-13 07.24.56.png

Clockwise or counterclockwise aligned text is obviously wrong scaled.

Message 25 of 25
(326 Views)