Get rid of the second LabVIEW window

[tst]

Has this ever happened to your application?

Well, it happened to me many times. I never figured out when this happens and when it doesn't, but I do know of a certain way to disable it - add the line HideRootWindow=TRUE to the application's INI file.

The problem with that solution is that when you build a new EXE, LV creates a new INI file which overrides the old one, unless you explicitly create your own INI file and tell LV to use it.

So, the solution to this is simple and this is the idea - LV should add the line HideRootWindow=TRUE to the application's INI file by default. Problem solved. Alternatively, maybe the whole root window thing is not needed anymore and NI can simply get rid of it.

[tst]

I don't remember seeing it in 2011 apps, but that doesn't mean it hasn't happened. Like I said, in any case in which it did happen, I just added the line and forgot about it.

[tst]

Grant, I'm attaching a small example project which shows this happening in LV 2011. Note that I've only seen it when I run the EXE on XP and that I couldn't test it other versions of LV. I'm assuming that in this case at least, it has something to do with how I handle the window (maximized, no title bar, etc.). Can you forward this to someone who can check it?

http://forums.ni.com/ni/attachments/ni/130/11145/1/Root%20Window%20Demo.zip

Also, I should point out that the program where I originally saw this actually runs on two XP computers which I think should be identical, but I only see this in one of them. I'm not sure what the difference is. Neither of them has the HideRootWindow line in the INI file.

[altenbach]

Is the runtime engine exactly identical on the two systems? (patchlevel, SP1, etc.)

Just wondering....

[tst]

The runtimes aren't exactly identical. Looking at lvrt.dll, the one which is currently fine has 2011f1 and the one that isn't has 2011f2. I would have expected them to share the installer, but I guess the second computer was brought in later and the installer was rebuilt.

Also, now I see that the computers themselves are not actually identical. They have different processors, different numbers of CPUs, different drives, etc., but they're both running XP SP3 32 bit. The one which is currently showing it is the quad core one (I say "currently" because I haven't checked that it's always the same one).

[tst]

I should probably also point out that I have limited ability to play with this. This is not a new program and it's running headless in the field, which is why no one noticed this. I had reason now to connect to the PCs, so I noticed this and modified the original project to create the sample project and run the test on them to verify that it happens.