LV main window: Always on the desktop

[billko]

---

@Yamaeda wrote:

---

@MimiKLM wrote:

Vincent,

I had to do the same, quick operation on the batch of VIs (around 60).

Each time I closed VI the Getting Started window appeared.

I've found it very annoying.

 That is the reason.

---

If you start a new project and then work on your VI's it wont happens, as it'll consider it project work. 🙂

/Y

---

Following your train of thought, wouldn't it be simpler to open a new VI and let it sit around minimized somwehere?  😉

[johnsold]

The context help for the Skip Getting Started window on launch item in Preferences (Tools >> Options on some platforms) states that LV will open with a new blank VI if the item is checked. It has worked that way since at least LV 8.2, which is as far back as I can easily check. Closing the last FP window brings the GSW window up even if that item is checked.

The GSW seems to be modal when called from the View menu, so you cannot keep it open in the background.

Lynn

[JÞB]

---

johnsold wrote:

The GSW seems to be modal when called from the View menu, so you cannot keep it open in the background.

Lynn

---

Hmmm.  I see no reason you couldn't grab a vi ref to the GSW an set the appropriate property.  I won't give specific directions.  Specific directions might cause some forum members to think changing this was "Safe."   It is NOT SAFE and I urge anyone to think carefully before making changes within "C:\Program Files (x86)\National Instruments\LabVIEW xxxx\resource\dialog\GS\GSW.lvlibp"

[tst]

OK, since this thread doesn't seem to want to die, I will just make the following comments:

1. Personally, I don't like the GSW, but since it's visible for so little of the time, I don't care that much.
2. If you want it not to appear, just make sure to have another window open (this can be a project window or a VI which is open in the main instance, as Bill suggested) and the GSW won't appear.
3. For the actual problem the OP had (performing the same operation on dozens of VIs), learning VI server is what I would actually recommend - it generally allows you to automate many kinds of operations in LV if you know the VI server hierarchy of classes, properties and methods.

[Yamaeda]

---

@billko wrote:

---

---

Following your train of thought, wouldn't it be simpler to open a new VI and let it sit around minimized somwehere?  😉

---

Good point, that's also a solution. I have a tendency to autoclose VI's though. 🙂

/Y