I believe that the OP is right in complaining, meaning that this is an issue that LabVIEW should be able to address. I also believe that unfortunately in the LabVIEW forums there is a tendency to blame the OP or to shift the problem to other programs, in this case Windows.
LabVIEW manages the Windows OS zoom very poorly. This is not only at runtime, but also the interface itself of LabVIEW suffers from using different OS zoom levels. I had reported this issue here and was quickly shot down.
But it does not have to be like that. I am using Google Chrome as an example. Chrome initially ignored the OS zoom level, so things would appear as if the computer was set to 100% zoom no matter what. The browser was then suddenly made to be aware of the OS zoom level. This caused a bit of an outcry, as users that had their WIndows zoom set to 125% (which is the default setting in Windows 7) suddenly were seeing everything larger. These was however a quick workaround, by adding this option: --high-dpi-support=1 --force-device-scale-factor=1. This made the program ignore once again the Windows setting.
For a program like LabVIEW the lack of such an option is a big problem. When I develop an application I do not know which zoom factor the final user will have. If the user buys a new monitor and uses a different zoom factor, the application appearance will change, rather unpredictably so, and there is nothing that a developer can do. This is not a good way of doing things. In my opinion I should be able to tell the user either a) make sure your windows zoom level is set to 100%, or b) activate this option to ignore the window setting and display it as 100%. Ideally there should be option c), which scales everything proportionally with the OS zoom level: this is ambitious but I have not seen many programs that deal with the OS zoom level as poorly as LabVIEW.
In summary, the OP has posted about a very real problem and right now LabVIEW is not able to deal with that problem satisfactorily.
