NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Resolve File Saving Conflict Dialog Box

Hi, I developed a new GUI for teststand. The problem is with the executable of the GUI, because at the end of the test it does not closed itself. I have to terminate the process by the TaskManager. 

When I used the GUI instead of the executable, it appears the dialog box attached. During the test some station globals are overwritten.

I am afreid that is the dialog box that stop the automatic closure of the exe.

 

Does anyone know how is possible to disable that dialog box?

 

Thanks a lot. 

0 Kudos
Message 1 of 21
(4,642 Views)
0 Kudos
Message 2 of 21
(4,642 Views)

Hi,

I think that the Dialog Box appears because you set the "Always prompt the user to resolve the conflict" option in the Type Properties>>Version tab for one of the types that is changing in your application. You can find more details in the following tutorial:

NI TestStand Type Management Best Practices

 

Serena

0 Kudos
Message 3 of 21
(4,621 Views)

This does not have anything to do with type conflicts.  You likely have two applications that are using the TestStand Engine.  One is completing and modifying the StationGlobals.ini file.  At the same time, your second application also is modifying the StationGlobals in a different way.  If you save the second application, it will overwrite what the first application did.  So you are prompted to decide which version you want to keep.  

 

This dialog occurs because there is code that calls Engine.CommitGlobalsToDisk.  This method has a parameter called "promptOnSaveConflicts" that gives the option to display this prompt.  However, I believe this method is likely called internally by the ApplicationMgr control.  I haven't found a way to have the ApplicationMgr call this function with a false parameter value.  Before shutting down your application, you could call Engine.CommitGlobalsToDisk with the false parameter and then shut down, which should make the problem go away.

 

However, you do risk overwriting global data so I would examine what you are doing to see if you expect to have multiple applications modifying the globals.   If this is unexpected, you likely have a problem.  I didn't quite understand the different between your GUI and EXE or what you are trying to accomplish, so perhaps there is a better way to implement what you want to accomplish.

0 Kudos
Message 4 of 21
(4,608 Views)

Hi, I've checked, but I tipically do not mark that flag. Anycase, I do not think this is the cause of my trouble. During the test I do not change any type palette and when I open the test sequence I do not have any type conflict.

The only thing I change during the test is the StationGlobals.ini. At the beginning of the test I overwrite it with the one of the customer and then during the test I change some value.

 

Thanks.

0 Kudos
Message 5 of 21
(4,608 Views)

It's got nothing to do with Type Palette. It's as Allen mentioned. Do you have the SeqEditor running as well as your GUI.

 

 

Regards
Ray Farmer
0 Kudos
Message 6 of 21
(4,599 Views)

Thanks Allen, what you posted me was very interesting and probably fix the problem on the dialog pop-up.

 

Unfortunately it does not fix my trouble. When the test is finished, everything shloud be closed, but the GUI.exe process still remain alive. I must kill it from the task manager.

The GUI.exe is the executable version of the GUI.vi. The GUI.vi works perfectly, at the end it closes everything.

I guessed that the root cause was the overwriting of the StationGlobals.ini, but is not it.

The problem is that I do not have any error message, and I do not know how to debug the GUI.exe.

 

Thanks a lot.

0 Kudos
Message 7 of 21
(4,595 Views)

No, both TestStand seq editor and Labview are not running.

 

Thanks Ray.

0 Kudos
Message 8 of 21
(4,595 Views)

Logatto,

 

What version of TestStand are you using?  What version of LabVIEW are you using?

 

The reason I ask is that If you use a User Interface that shipped with TestStand 3.5 or before with LabVIEW 8.0 or later, the problem of all windows closing but the application staying open may happen. (The reason this happens is that the LabVIEW UIs shipped with TestStand 3.5 didn't close a reference in a certain location.  LabVIEW 7.1.1 was tollerant of this so it was OK when it shipped, but LabVIEW 8.0 changed behavior).

Josh W.
Certified TestStand Architect
Formerly blue
0 Kudos
Message 9 of 21
(4,590 Views)

TestStand 4.2.1 and Labview2009.

 

Thanks

0 Kudos
Message 10 of 21
(4,587 Views)