LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
tst

Get rid of the second LabVIEW window

Status: New

 

Has this ever happened to your application?

 

RootWin.PNG

 

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.

 

 


___________________
Try to take over the world!
15 Comments
altenbach
Knight of NI

Is this still a problem? I haven't seen the root window in ages and did not do anything special.

 

Also, whe you built an application, you can specify a custom configuration (*.ini) file in the "advanced" section. Did you try that?

tst
Knight of NI Knight of NI
Knight of NI

Yes, it is still a problem. It doesn't always happen, but it does, at least in 2009. I assume there is some logic which governs this (e.g. one of the window settings for the main VI), but I don't know what it is.

 

As for creating a custom INI file, I did mention that in the idea. I don't want to have to create a special file for every project and I can't use a generic one because each file needs a section which has the same name as the EXE.


___________________
Try to take over the world!
dthor
Active Participant

I still see it every once in a while in 2010.

altenbach
Knight of NI

So, since it typically does not appear, maybe this should be a bug report instead of an idea.

 

This ini entry is typically not needed, so maybe there is something else wrong under some poorly defined condition. Can we narrow this down?

tst
Knight of NI Knight of NI
Knight of NI

I'm hesistant to report this as a bug because someone at NI might decide this isn't a bug and close it as such. Adding the INI key seems like a minor change which does not even require looking into the code to figure out when this does or does not happen.


___________________
Try to take over the world!
G-Money
NI Employee (retired)

So we see the behavior in 2009 and 2010 but its intermittent. Any other trends (e.g. only on XP) that could help narrow down the issue? I agree that this probably should be a bug report since the issue is only intermittent. I would be worried if R&D really just starting adding in an ini token to newly built executable instead of figuring out what's really going on. I'm not trying to nitpick here but it almost seems like the idea is to incorporate the workaround for this issue into the whole product while they work on it. Could be an option though if enough people run into the issue.

tst
Knight of NI Knight of NI
Knight of NI

I don't know if this is intermittent on not. It definitely does not always happen, but in places where it did happen, I just added the line to the INI file and forgot about it, so I don't know if for a specific EXE this would be intermittent or not. Since I don't know what the logic is for having the second window and I don't know of any downside to having the INI key, I would prefer having that as a quick solution than something which would require digging through the code.

 

I can say that there was a recent EXE where I saw this happening on XP. I ran a more recent build of that EXE on Win 7 without the INI key and didn't see it, but it's quite possible I changed the window settings since then. I would have to try the new version on XP to see if it happens there.


___________________
Try to take over the world!
Mark_Yedinak
Trusted Enthusiast

I have seen it quite often and in versions older than 2009. I believe I have seen it as far back as 8.2. I called tech support about this years ago and even gave them a very simple project that reproduces the issue. I would love to see this fixed.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
SnowMule
Active Participant

YES! 

 

It's something I've just "dealt with", but do find annoying.

 

100th kudo from me.

G-Money
NI Employee (retired)

I haven't seen this anymore in the past couple releases of LabVIEW (2013 and 2012). It appears that the HideRootWindow ini token wasn't added to the generated ini file but maybe the underlying issue has been fixed. Has anyone noticed this in newer versions of LabVIEW? If not, we might want to consider closing this idea.