Panel Position default to Primary Monitor

[JÞB]

We have all seen it.  Most of us have done it.  a vi is saved with the BD or FP positioned on the secondary monitor and deployed to a single monitor system.  Opening the vi saved this way IS cought and the vi opens with a portion of the panel visible on the monitor. We DO have the Windows run-time position properties (And that saves a lot of trouble in the field for deployed GUIs) but we still have the development enviornment to consider.  A Config option to "Allways save LabVIEW Panels on primary monitor" would be a real hassle saver.

[crossrulz]

At the very least, when moving to a 1 monitor system, put the window fully on the primary monitor with the position it had on the second monitor.

[Intaris]

One could use a "In range and coerce" on the mionitor number limited to the number of physical monitors available.... Got my vote.

That would put a VI saved on monitor 3 on monitor 1 if only 1 is available, and on Monitor 2 if only 2 area vailable and so on.

[fefepeto_kb]

What crossrulz added could be easily done in Windows 10 and above with the following shortcut key: Windows Button+Shift+Left Arrow to move the window to a monitor with smaller ID, and Windows Button+Shift+Right Arrow to move the windows to a monitor with higher ID.

---