LabVIEW
LabView windows won't stay on screen in 2 screen windows system
I'm not sure about your chances of forcing it directly with an ini key or similar, but I think I remember that LabVIEW preferentially tries to stay on the screen it considers primary when it is opened.
You can manipulate this I think - probably you can do it by renumbering your screens or turning one off when you open LabVIEW, but it might also be possible to drag the launcher onto the second, then close it, and reopen? I want to say I have a vague memory of this, but...
Unfortunately, I don't do this often enough to remember, and I try fervently to keep everything on my main screen, because VIs will reopen wherever you last saved them, and if that is on "screen 2", then when you open them on a different computer without a second screen, or with different resolutions, it often ends up partially/mostly off-screen, which is a pain.
Regarding "other development tools", I guess most don't open a whole bunch of separate windows. Of those that I can think of that do, they often default to throwing "new" windows on the main desktop...
LabVIEW follows that convention too but each LabVIEW window is its own window which remembers where it was open when it last was saved. But this is not screen number based but simply screen location based. Your multiple screens also form simply a larger virtual screen and the screen coordinates LabVIEW remembers are based on this virtual screen with no monitor number whatsoever
And unlike other applications who will often happily open their windows completely offscreen if you don’t have that monitor connected, LabVIEW will actually move it’s windows on opening in such a way that they are partly visible on the nearest corner of the connected screens to where they were supposed to be placed.
But LabVIEW is (thankfully again) not a MDI application with one main window that forces everything inside it. Each window is its own entity and maintains its own screen location even across sessions. Of course while the thinga like Toolpalette always maintain their last state, VIs need to be saved to remember a particular location.
There is an option in a VI’s properties to change the screen number and location explicitly but that is for runtime location when the VI is executed or programmatically popped up during execution of your application.
@rolfk wrote:
LabVIEW follows that convention too but each LabVIEW window is its own window which remembers where it was open when it last was saved. But this is not screen number based but simply screen location based. Your multiple screens also form simply a larger virtual screen and the screen coordinates LabVIEW remembers are based on this virtual screen with no monitor number whatsoever
And unlike other applications who will often happily open their windows completely offscreen if you don’t have that monitor connected, LabVIEW will actually move it’s windows on opening in such a way that they are partly visible on the nearest corner of the connected screens to where they were supposed to be placed.
But LabVIEW is (thankfully again) not a MDI application with one main window that forces everything inside it. Each window is its own entity and maintains its own screen location even across sessions. Of course while the thinga like Toolpalette always maintain their last state, VIs need to be saved to remember a particular location.
There is an option in a VI’s properties to change the screen number and location explicitly but that is for runtime location when the VI is executed or programmatically popped up during execution of your application.
I was one of those who actually liked that NXG put all your windows in one parent window.
