LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Messed up text on Windows 10 machine

Solved!
Go to solution

I am guessing one of the Champions has the ability to move this thread to somewhere "safer" if others feel we might have someone breaking stuff.

 

Yeah, laptop has been rebooted, is at 100% screen vs 150%, etc., though I do switch back and forth as 1920X1080 and 17" screen becoming small for my aging eyes. Going to "steal" one of the son currently residing here's larger ones, though it won't be any of his three ginourmous ones. He is doing support remotely for one of the local Uni, room looks like an updated Star Trek bridge, lol.

 

For those that don't know me, I have been LabVIEWing since the Fall of '92, from Windows 3,1 (LabVIEW 2.2, blech!!) , SunOs, Mac OS, RT, etc., so not my first rodeo. I do appreciate any and all suggestions though, sometimes thinking about the answer, or questions posed about my question, will lead to thinking at an angle from original thoughts. I will say, my questions on these Forums usually indicates I am, at least temporarily, baffled.

 

Thanks!

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 11 of 24
(1,195 Views)
Solution
Accepted by topic author LV_Pro

You haven't really said if you played with labview.ini yet as others have suggested.

 

I can reproduce your screen by setting the "appFont" to e.g. size 33. (No changes in windows scaling, etc)

 

altenbach_0-1615998701793.png

 

OTOH, doing the same to systemFont, messes up the menu:

 

altenbach_1-1615998826276.png

 

 

Message 12 of 24
(1,191 Views)

Thank you Christian.

    Apparently LabVIEW on my machine wasn't happy with the default Windows10 App font or its size. I don't know what that is or what size it is normally, but online seems to indicate that it is Segoe UI

putting this line in the LabVIEW.ini file:     appFont="Segoe UI" 18 gives me this:

 

LV_Pro_0-1616443273367.png

Interestingly, messing with the text size setting in "Settings", "Ease of Access" changes the Windows 10 text size, such as File Explorer, but didn't effect the Project display above. I also just decided that I like the Arial font, at least for the moment.

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



Message 13 of 24
(1,148 Views)

Ok, Christians suggestion provided a partial solution, but I am still seeing messed up windows in LabVIEW, in fact in initial project and help screens.

 

 

LV_Pro_0-1618506451866.png

 And at the initial New Project level. This is LabVIEW 2018 (32bit) on a Windows 10 machine

 

LV_Pro_1-1618506539161.png

 

Currently my actual project menus look ok with the following in the LabVIEW ini file

 

appFont="Arial" 18
systemFont="Arial" 18

 

Thanks again.

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 14 of 24
(1,102 Views)

Just opened LabVIEW 2015 with the same results on both the screens shown before.

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 15 of 24
(1,091 Views)

Any thoughts or pointers to where LabVIEW dev system gets font info for the LabVIEW system screens, such as examples menu display. Really painful trying to use them, and the problem occurs in 2015 and 2018 (32Bit) LabVIEW and 2018 (64bit) just now.

 

LV_Pro_0-1619626110445.png

 

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 16 of 24
(1,058 Views)

This is getting really frustrating, hard to use some of these built in stuff!

 

LV_Pro_0-1619651837071.png

 

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 17 of 24
(1,044 Views)

Each version has its own ini file and for each version there is one for 32bit and one for 64bit (depending on what's installed). Did you update all?

 

Also, size 18 seems a bit large.

0 Kudos
Message 18 of 24
(1,041 Views)

I've seen some similar things where it didn't seem to adhere to the windows Scaling, but using Custom scaling and setting the same value worked. 

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 19 of 24
(1,023 Views)

Christian,

    The problem is identical with LabVIEW 2015 (32 byte), 2018 (32) and 2018 (64). I had made the changes to the 2018 (32) ini, and it resolved some of the problems, all of them show the issues shown. I shouldn't have to change the ini, it should work, I am using Windows 10. I don't have this issue on my Windows 7, didn't have to make changes to the ini to accomplish this.  If am I having problems, how is someone without 25+ years LabVIEW supposed do this?

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



0 Kudos
Message 20 of 24
(1,011 Views)