How to remove the extra window when I start LabWindows/CVI or am executing my program?

[RobHoi]

For a short while (maybe a week or more) I get an additional small window behind my application. Also, when I start LabWindows/CVI I get the same window. It is a small, empty window with the same title as the application. Pressing close (X) closes the application too.

I cannot remember that I have seen this before and do not know what has changed on my PC. It also happens with old (previously compiled) LabWindows programs, so it seems that something in Windows has changed.  I use Windows XP and LabWindows/CVI 9.0.0 (348).

Thanks,

Rob

[gdargaud]

Is it a console window ? If so maybe you clicked on [Console application] in the [Target settings]. I think sending anything to stdout also brings up that window.

[RobHoi]

No, it is no console window. Executables that previously (last year) not had this extra window now have.

Also the LabWindows/CVI environment itself now has got such a window...

[gdargaud]

Screenshot ? Is there something on the Windows taskbar ? A debugging window maybe (DrWatson or something).

[RobHoi]

Title of small box is identical to name of the Labwindows environment, or as the title of the executable, if another LabWindows generated executable is started instead..

With processExplorer can be seen that no other processes are started additionally.

If  minimize is clicked, the application will minimize, but the small box stays. If close is clicked, the program will close.

[D_Biel · Accepted solution]

Hi Rob,

The window you are seeing is part of the CVI. It is the parent window to all CVI windows both in the environment and at run-time. Typically, this window is hidden way off screen so that you don't even know it is there. But some video adapters have a setting that forces all off-screen windows to move on-screen. Take a look in your video adapter settings to see if this setting exists on your driver. If it does, then disabling the setting will allow the window to hide off-screen.

[RobHoi]

Hi,

Thank you for the solution. It was indeed caused by the nView desktop manager.