LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

What Monitor / resolution do people recommed

For many years my favorite monitors were 24" 1200p (1920x1200 0.27mm pp).

 

Customer requirements forced me to go to 27" QHD (2560x1440 0.2331mm pp).
I didn't like the smaller pixels at all.

 

Recently, I swapped out 2 of these 27" monitors with 32" QHD (2560x1440 0.2727mm pp).
Once again I'm a happy camper. (LG QHD 32" 32QN600-B, IPS for about $210 on sale.)

 

Multiple monitors are much better than 1 big one IMHO.

People that I know using higher res monitors end up resorting to scaling so what's the point?

 

Consider pixel pitch and get good quality (IPS) screens.

----------------------------------------------------------------------------------------------------------------
Founding (and only) member of AUITA - the Anti UI Thread Association.
----------------------------------------------------------------------------------------------------------------
Message 11 of 14
(176 Views)

With later versions of LV you can zoom the BD in and out as needed.  Maybe with this feature you can avoid humungous BDs on huge screens by agreeing on how many "zoom factors" to use for each monitor size.  But really, you shouldn't even be approaching one screen size at 1080p.  That's a sure sign that your VI is doing too many things and should be broken into subVIs.  I believe that you should strive for "one function per VI".  For instance, "acquire data", "process data", and "display data" would be three subVIs.  Of course, I also believe that (ideally) there should only be subVIs in your top level VI.  In fact, you can even encapsulate your top level loops as subVIs if you have a lot of them.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 12 of 14
(171 Views)

@stevem181 wrote:

For many years my favorite monitors were 24" 1200p (1920x1200 0.27mm pp).

People that I know using higher res monitors end up resorting to scaling so what's the point?


I will try to explain what the point is. Let's say I'm working on my (or your) favorite monitor with a 0.27 mm pitch (my DELL U3011 has 0.25 mm, I guess).Well, it's 0.27 mm per pixel. I will illustrate this with LabVIEW NXG because only this version of LabVIEW can be "scaled" properly due to its internal use of .NET/WPF.

The T/F Selector in LabVIEW NXG looks like this in comparison with LabVIEW Classic when displayed in 100% 1:1 side by side:

Screenshot 2024-11-19 06.28.48.png

This icon takes up 40x40 pixels (slightly larger than Classic), which is 0.27 x 40 = 10.8 mm of physical space. I think if you measure this screenshot with a measuring tape directly on the screen, you'll get around 10x10 mm.

Now I'm moving to my DELL Laptop with 3840 x 2160 resolution on a 15.6-inch screen. If I continue to work in 100% mode, then with a 0.09 mm pitch, this icon will take up only 3.6x3.6 mm. You'd need good eyes and a steady hand to use it. To get back to my 10.8x10.8 mm size, I'll set the scaling to huge 300%. Now I'll get my "old pitch" back. But the key difference is that now this icon will take up 120x120 pixels on the screen instead of 40x40 before! And all icons, texts, etc. will look like much sharper because of this:

 

Screenshot 2024-11-19 06.49.41.png

That is the difference. If I enlarge the question mark, I will see that everywhere I had a single monitor pixel before, I now have three, because of 300% scaling:

 

Screenshot 2024-11-19 07.06.24.png

But this possible only if everything is vector and resampled properly.

 

0 Kudos
Message 13 of 14
(160 Views)

@billko wrote:

With later versions of LV you can zoom the BD in and out as needed.  


It is not the best implementation. I using this rarely and occasionally, but to work continuosly in zoomed mode is just hell. And most of icons are very unsharp, because are not vector. This is how screenshot above looks in 250%:

Screenshot 2024-11-19 07.15.39.png

Very bad. In additional, in some cases there are performance penalties (was discussed on this forum already).

0 Kudos
Message 14 of 14
(155 Views)