XControl becomes permanently locked every time VI containing it is run.

[Mike_Le]

I have an XControl dropped onto the front panel of a VI. When I run the VI, everything functions as expected. I stop the VI (without using "abort").

Now I want to unlock the XControl so  I can make some changes. I right-click the "Unlock library for editing" from the project window and get a "Stop Running VIs" prompt, which lists four VIs - all of them methods of the XControl library.

I can close every open window and nothing's running. I have to close the project and reopen it before the XControl becomes unlockable again.

I would attach code but I'm using a lot of typedefs, OpenG add-ons, and a suite of custom sub-VIs used in our company as "common code." If no one has any troubleshooting suggestions, I can try recreating a simplified version of the problem.

[GregFreeman]

Have you tried reproducing it yourself, simply by making a new VI with only a while loop, and dropping the x control on the front panel then running/stopping it? Do you have anything in your x control that could cause it to get "stuck" in its loop? Remember, the x control runs in its own context (not sure if context is the correct word here) so just because your program is stopped doesn't mean the x control code has stopped running.

[Mike_Le]

Yes, that's exactly how the VI I'm running is setup. I have a simple demo VI containing nothing but the XControl, a while loop, and a stop boolean.

[Mike_Le]

As far as anything that might be holding the XControl up, I don't think so. As far as I can tell, its block diagram has stopped.

[PackersFan]

Are you sure that you are not spawning any parallel VIs from the XControl that might still be running?

[Mike_Le]

How would I check for that?

None of the XControl methods in the VI seem to be running when I open them, though they do appear locked (since the library is locked). I'm not doing anything fancy like performing asynchronous calls. Each of the XControl methods should execute and shut down cleanly and there are no while loops or "wait on queue" actions, etc...

[GregFreeman]

That's bizarre. If you don't get any response on here that's satisfactory, I'd suggest just calling in to the AE department and trying to get them to troubleshoot it since it's reproducable.