[jgcode]

[cross-posted to ni.com]

Howdy !

I have run into the following issue when creating a tool for LabVIEW that continually runs in the background (daemon/process VI):

By default, LabVIEW shows the GSW when all other files (project, VIs etc...) are closed.
However with the process running in the background, it does not show the GSW!

Has anyone run into the issue before?
Is there a way to set LabVIEW to 'ignore' my Tool and get the GSW to show normally?
The VI is running in the NI.LV.Editor application instance (the Tool is launched by Quick Drop).

Cheers

-JG

[Ton Plomp]

jgcode, on 23 July 2010 - 11:06 PM, said:

By default, LabVIEW shows the GSW when all other files (project, VIs etc...) are closed.
However with the process running in the background, it does not show the GSW!

You could explore some of the application properties, if I'm not mistaken there's a 'private' or 'system' property that should make it invisible for the GSW.
Or you could launch the GSW. There is a menu launch token for the GSW that loads it into the front.

Try to get Christina into this discussion, since she wrote a lot of code for the GSW.

Ton

[jgcode]

Ton Plomp, on 24 July 2010 - 07:19 AM, said:

You could explore some of the application properties, if I'm not mistaken there's a 'private' or 'system' property that should make it invisible for the GSW.
Or you could launch the GSW. There is a menu launch token for the GSW that loads it into the front.

Try to get Christina into this discussion, since she wrote a lot of code for the GSW.

Ton

Thanks Ton,
I don't want to manage showing the GSW etc, I am hoping it can be all handled by LabVIEW by flagging that VI to be ignored or something similar.
I will check out the app props, in the meantime I have contacted Christina.

Cheers

-JG

[Christina Rogers]

The Getting Started Window will not reappear if there are any open or hidden LabVIEW windows. If your background-running VI never opens its front panel, or closes it using the FP.Close method, it should not prevent the return of the GSW.

If your VI closes its window and the GSW is still failing to appear, you may have found a bug where LabVIEW is not checking the window list at a time that it should. If that's the case, PM me and we'll investigate.

[jgcode]

Christina Rogers, on 25 July 2010 - 04:48 PM, said:

The Getting Started Window will not reappear if there are any open or hidden LabVIEW windows. If your background-running VI never opens its front panel, or closes it using the FP.Close method, it should not prevent the return of the GSW.

If your VI closes its window and the GSW is still failing to appear, you may have found a bug where LabVIEW is not checking the window list at a time that it should. If that's the case, PM me and we'll investigate.

Hi Christina,

Thanks for your reply.
That is good to know the exact criteria - which is what the issue would be here:

My process does have a GUI so the FP can be opened, therefore I use the FP.Hidden state to hide the window in-between calls.
(I was thinking it may be faster to load and I was also experiencing some issues using FP.Close and memory that I have since fixed)

Anyways, I have changed this around now so the FP.Close is called each time and now the GSW window pops up with the process still running in the background!

Thanks heaps!!

[Christina Rogers]

jgcode, on 25 July 2010 - 11:01 PM, said:

Thanks heaps!!

You're welcome! Glad I could help.