Rif.: Resolve File Saving Conflict Dialog Box

[AllenP]

Is the GUI.exe left alive on purpose?  Killing a program using Task Manager does not sound like something that is normal.  Is this the sign of a different problem? 

The overwriting of the Station Globals sounds like it is happening from running the GUI.vi and GUI.exe at the same time.  Both will write the Station Globals when they shut down.

When does the dialog box appear?  When you run both of them at the same time?

[logatto]

Hi, I do not think more that the cause of my problem is a matter of SationGlobals.

At the beginning when I closed the GUI.vi appeared the File Saving Conflict Dialog Box. Then I guess it was the cause of problem on closure of the GUI.exe 

But when I used the Engine.CommitGlobalsToDisk the dialog box at the closure disapperad.

Hence, I guess there is something more that is not correct, but I do not know how debug it because the problem at the closure occurs with the GUI.exe but not with the GUI.vi.

Thanks.

[AllenP]

The dialog box itself says it's due to Station Globals.  I'm not sure what more can convince you that is the cause of the dialog.

Now, the reason they are being modified by another process may be due to something unusual going on.  I'd like to understand more about what you are doing when this happens.  Can you reproduce the problem reliably?  If so, what are the steps you take? 

[Manooch_H]

Logatto -

You're likely running into a known issue (191678). Let me ask you, how are you telling the application to close? Are you click the close button in the title bar (usually a red box with an x in it)? Are you clicking an Exit button of some sort? When you perform the action that is intended to close the application, is your mouse hovering over the application or is it somewhere else (perhaps empty space on the desktop)?

If this is the issue you are running into, hovering the mouse over the application should cause the application to close. Please let me know if this is in fact the issue you're experiencing and I will provide some possible workarounds for you.

[logatto]

Hi Manooch_H, I do not have problem with mouse position. I can close the GUI.exe both using Exit button and the red X in title bar. When I click the GUI.exe is closed by the method "FPclose" but I can see the task active into the Taskbar in the bottom (like a window minimized). And in I open the task manager I can see the process GUI.exe is still alive.

AllenP, since I used the method you suggest me the dialog box no longer occurs. When I close the GUI.vi there are no more dialog boxes and everithing closes properly.

Thanks.

[Manooch_H]

logatto -

Any way you could provide a set of files that reproduces this behavior so that we can investigate it?

[AllenP]

When you call FP.Close, are you expecting your GUI to stop running?  You'll need to actually exit the application if you want the process to end.  If this is intentional, is there a reason you want to keep it open?

[logatto]

Substantially the ShutDown.VI is almost the same than the original. This is the last subvi the main call, and the FP.Close is tha last action.

The subvi with the red icon is just to close the splash screen.

I launch some VIs with Vi server method. But when the closure command arrives I close all these VIs before the GUI.vi closure. Infact, when I close the GUI.vi everything closes properly and I can close also Labview without any problem. If I had some VIs running I couldn't do it.

Thanks.

[Manooch_H]

logatto -

In all honesty, the fastest way for us to get to the bottom of this issue is to be able to reproduce it on our end. Could you provide your files or an example set of files that reproduce this behavior? If you're hesitant to post the files to this discussion forum thread, I can ask the forum administrator for your contact information and contact you directly.

Please let me know how you would like to proceed.

[logatto]

Hi Manooch_H, I percectly know that the only way for you to fix the problem is debug the code. The matter is that, as you know, the TestSatnd user interface is not a simple VI. In order to run the GUI you need several LV library, precess model and machine sequence, type palettes. You should recreate my entire sw environment.

It's a big effort. Let me see what I can do in next days.

Thanks a lot.