LabVIEW DISP.ALLMONITORS property vs. Windows IDENTIFY

[code-lux]

here you go with LV2018

[CoastalMaineBird]

My guess is that it has to do with the Primary Monitor.

I can change the primary monitor, and my LabVIEW code does nothing different, except draw the red ring around the new primary.

[zou]

---

@CoastalMaineBird wrote:

My guess is that it has to do with the Primary Monitor.

I can change the primary monitor, and my LabVIEW code does nothing different, except draw the red ring around the new primary.

---

I tried the same thing.  No change.

It seems NI defines their own screen#.  The array index IS screen#.

Could someone test this on other OS?

[CoastalMaineBird]

The array index IS screen#.

Yeah, that's where my LV code gets the "Monitor 1" string.

But why is Windows Different?

If I unplug one of the monitors, the orientation rearranges itself into whatever order it feels like.  But the numbering between Windows and LV is still different.

If I plug it back in, it returns to the way it was before, still different between Win and LV.

[CoastalMaineBird]

If I unplug TWO monitors, and then plug them back in IN A DIFFERENT ORDER, then Windows doesn't change the ordering, but LabVIEW DOES !

[zou]

> If I plug it back in, it returns to the way it was before, still different between Win and LV.

Maybe other OS handles multiple monitors different from Windows.

[rolfk]

LabVIEW simply uses the multimonitor API of the underlaying platform. In Windows this is EnumDisplayMonitors() https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-enumdisplaymonitors

Unfortunately it uses a callback function so is pretty hard (not impossible but very cumbersome) to interface through it through the Call Library Node.

[zou]

The .net method returns exactly the same results as LabVIEW (tested with 3 monitors).

[zou]

I found this on MS web site:

https://learn.microsoft.com/en-us/answers/questions/1572062/how-to-get-the-monitor-number-displayed-...