How do I hide the VI loading window for an exe file when deployed

[aeastet]

Is there some set point or registry entry that I need to switch to hide the vi load window when an exe is executed?

[JÞB]

---

@aeastet wrote:

Is there some set point or registry entry that I need to switch to hide the vi load window when an exe is executed?

---

several years ago Mark and I shared a cube wall.  (actually, several cube walls over the years)  He developed 1 example of a splash screen that has been available for use to hide the loading window.  I haven't looked too deep in it for several years but It worked! 

Splash screen example code

[aeastet]

That is not what I am talking about. When you first click on the exe the VI loading window pops up to show that you are loading 356 of 890 vi's in your project. I have a nice splash screen I just have that ugly windows loading vi's window that I need to get rid of. any ideas on that? I am assuming that you can hide that I could not find the way myself.

[aeastet]

---

@Jeff Bohrer wrote:

---

@aeastet wrote:

Is there some set point or registry entry that I need to switch to hide the vi load window when an exe is executed?

---

several years ago Mark and I shared a cube wall.  (actually, several cube walls over the years)  He developed 1 example of a splash screen that has been available for use to hide the loading window.  I haven't looked too deep in it for several years but It worked! 

Splash screen example code

---

I actually have the splash screen vi's that you are talking about and that is what I based mine on. It is nice to have that code to see how others would do it. So thanks Mark for the push in the right direction on this.

[JÞB]

---

@aeastet wrote:

---

@Jeff Bohrer wrote:

---

@aeastet wrote:

Is there some set point or registry entry that I need to switch to hide the vi load window when an exe is executed?

---

several years ago Mark and I shared a cube wall.  (actually, several cube walls over the years)  He developed 1 example of a splash screen that has been available for use to hide the loading window.  I haven't looked too deep in it for several years but It worked! 

Splash screen example code

---

I actually have the splash screen vi's that you are talking about and that is what I based mine on. It is nice to have that code to see how others would do it. So thanks Mark for the push in the right direction on this.

---

OK- so another method that we tossed about. was to place a simple vi AS main with a FP that "Looked" like a splash screen.  use THAT vi to dynamically load and run the real main vi for the application with a vi server ref (wait for completion F auto dispose T) and then close itself after a delay.  We debated that the method was "cheesy" and required a dynamic call to the real top level VI so it was easy to botch the build spec.  but we did try it and it hid the Loading screen effectively

[aeastet]

So as far as you know there is no INI file setup or Regisrty entry that we can change to make that hidden? That seem like something that should be a no brainer for NI.

[JÞB]

---

@aeastet wrote:

So as far as you know there is no INI file setup or Regisrty entry that we can change to make that hidden? That seem like something that should be a no brainer for NI.

---

Could be an Idea

But, I whipped up an example launcher.vi

change the file constant of course, optionally, wait on the notifier to set FP open or abort the main on error.  Add this in the main.vi after any init code. 

[MrYoung]

Simply add: 

ShowLoadProgressDialog=False

to the INI file that is in the same directory as the EXE.

[DougShuffield]

I can't get the ShowLoadProgressDialog=False to work in an old 8.5.1 project.  What can I do in 8.5.1 to hide the main vi loading splash screen?  The issue is that I don't want the operator to be able to hit the "Stop..." button while the application is loading subvis.

- Doug

[mirola]

Hi Doug,

According to my experiences, the loading window appears in the moment some file is not located in the expected folder (but found in another one, otherwise a dialog would pop up). This happend to me with DLLs, typically.

Try placing all the support file in the the sub-folder \data of your application folder, or directly into the application folder if you don't create the data folder.

Further, save the VIs that find some sub-VIs or support file somewhere else than expected when you load the project/main VI before building the executable.

Best

mirola