stop button grayed out after a new instance is launched

[Kimberly_Wenger_Austin]

HI lavalava,

I was able to run the VI and see the error that you were seeing, so now I am just trying to pinpoint where the error is coming from.  I would like to file a bug report for this issue, but I need to be able to recreate the issue from scratch.  It seems like you are very familiar with LabVIEW, so have you seen this behavior in any other reentrant vi's?  Have you seen it when incorporating Xcontrols before? Thanks so much!

Kim

[lavalava]

---

@VTKim wrote:

HI lavalava,

I was able to run the VI and see the error that you were seeing, so now I am just trying to pinpoint where the error is coming from.  I would like to file a bug report for this issue, but I need to be able to recreate the issue from scratch.  It seems like you are very familiar with LabVIEW, so have you seen this behavior in any other reentrant vi's?  Have you seen it when incorporating Xcontrols before? Thanks so much!

Kim

---

Hi, Kim.  I've only seen this issue whenever you're embedding a multifunctional xControl such as the one in the attachment.  And it doesn't have to be a complicated xControl too.  However, if you're using a very simple single function xControl, you won't see this problem. 

Also, I noticed that whenever I cloned a VI with "Auto Dispose Ref" option on such as the attachment and I close the newly created instance (clone), I can't edit the original VI.  Sometimes, it gets stuck inside the system memory and Labview won't let me edit the original file.  It would be nice if NI could implement a feature where we could manually select from a list and release the VI or instances of that VI from memory.  That way, we don't have to restart Labview just to edit a file.

Thank you for the help.

[Kimberly_Wenger_Austin]

Hi lavalava,

Thanks for that information.  I think I have all that I need to reproduce the issue and file the bug report on our end.  As far as the VIs that are stuck in memory, I have noticed that with your VI and I noticed that the VI stuck in memory was the image.vi.  I know this will not solve the issue, but this example will show you the VIs that are saved in memory and while it is not a fix, it may help.  Also, I am not sure if it is just the front panel that is in memory, but this VI will clear the front panel and potentially unlock the Xcontrol.  (Be sure to right click the VI and Save Link As...).  I hope this helps!

Kim