stop button grayed out after a new instance is launched

[lavalava]

The stop button gets grayed out after a new instance is launched.  Could someone please help me out?  Just a screenshot reply will do just fine since I'm still using v8.6.  Thanks.

[Mark_Yedinak]

I'm not sure why that stop button looks different but I would recommend against using that to actually stop your VI. The stop (or more accurately abort) button should be used during development. If the user is interacting with the VI then you should use an actual button with code to perform any necessary cleanup. The abort button kills the VI immediately and doesn't perform any cleanup.

[RavensFan]

You have a reentrant VI.  So there is a clone everytime you call that VI.  You are probably looking at the master copy of the VI.  The buttons show it is executing, but since it is not any one of the particular instances, the Stop button is an invalid choice.

Are you saying the Stop/Abort button is still killing the VI?  That isn't doing it on my LabVIEW.  What version of LV are you using?

[lavalava]

The original VI that is being cloned does not have this issue.  The stop button is not grayed out.  I still need a master /global stop button.  Not too worrying about garbage buildups because I have a cleanup subroutine that automatically cleans everything up once you click on the play button again.

8.6.  The stop button isn't killing or hurting anything.  It still works like normal even though it was grayed out.  I've created new instances with this same method before and I've never run into problem except for this VI.  Unfortunately, I can't create a new VI either since my program has gotten too big.  I'm sure there is class method somewhere that allows me to prevent the stop button from graying out.  I just don't know it yet ...but the answer is out there.  I'm sure someone knows.  

[Kimberly_Wenger_Austin]

Hi lavalava,

I cannot seem to reproduce your error even after changing a lot of different options within VI Properties for the reentrant VI. Can you post your code (or create a simple set of VIs that behave the same way) to the discussion forum?

To start troubleshooting this issue, here is a screen shot of my VI Properties>>Execution for the reentrant VI.  Are your settings the same? (they may be in a slightly different location since this is in LabVIEW 2010)

I hope this helps!

Kim W.

[lavalava]

Hi, Kim.  Sorry for the late reply, I didn't think anyone would respond so here is the best I can replicate. My LV version is 8.6.1 running on XP x64.  This problem frequently occurs whenever you're using multifunctional xControl. 

 

When you download the attachment, please keep them all in the same dir then run "run.vi" file.  Thanks for the help.

[Darin.K]

I have not tested your code, but if that button is functional, but greyed out I wonder if it is simply a redrawing issue.  If you force a window redraw (ie. drag another window over it), does it redraw greyed out?

[lavalava]

---

@Darin.K wrote:

I have not tested your code, but if that button is functional, but greyed out I wonder if it is simply a redrawing issue.  If you force a window redraw (ie. drag another window over it), does it redraw greyed out?

---

Yes, you're right it is a redarwing issue.  What you've described is exactly the issues I've ran into.  It's really hard to explain that the end users, I have explained to them and they just stared at me with (!).  And secondly, if you drag the new instance over previous instance (i.e., window), it just going to cause everything to slow down and not ticking at exactly 100ms, slow everything down to more like 3s per tick depending on your CPU.

[Kimberly_Wenger_Austin]

Hi lavalava,

I have looked over your VI and tried to run it and while I can run your VI and get the same error, when I try to recreate it in a new VI, I cannot recreate the issue.  The only difference between your test.vi and mine is that I am not calling the Xcontrol. I am calling the same set of 4 random number generators and putting them into a cluster, but I am not referencing the RNG cluster.  I think this is where the issue lies and it is possible that you Xcontrol is corrupt.  While I could find the Data 2 that shows up in the test.vi, I couldn't find the image.vi  Where are you calling the image.vi? 

Also, have you tried developing your program on a different operating system?  LabVIEW is not supported on Windows XP 64 bit, and while it seems to operate fine in most cases, there are definitely a few instances that will have unexpected behavior in the XP 64 bit environment.  Thanks!

Kim W.

[lavalava]

---

@VTKim wrote:

Hi lavalava,

I have looked over your VI and tried to run it and while I can run your VI and get the same error, when I try to recreate it in a new VI, I cannot recreate the issue.  The only difference between your test.vi and mine is that I am not calling the Xcontrol. I am calling the same set of 4 random number generators and putting them into a cluster, but I am not referencing the RNG cluster.  I think this is where the issue lies and it is possible that you Xcontrol is corrupt.  While I could find the Data 2 that shows up in the test.vi, I couldn't find the image.vi  Where are you calling the image.vi? 

Also, have you tried developing your program on a different operating system?  LabVIEW is not supported on Windows XP 64 bit, and while it seems to operate fine in most cases, there are definitely a few instances that will have unexpected behavior in the XP 64 bit environment.  Thanks!

Kim W.

---

Hi, Kim.  It sounds like you were never able to run the attachment to see the actual problem.  This is simply a drawing issue with Labview.  I have already tried this on XP x64, XP x32, Vista x86, Vista x64, and 7 x86.

The image.vi is inside "RNG" folder.  All the files you needed to run the simulation should be included in that attachment above.

Thanks