Error when I Unlock Library for Editing with XControl

[elset191]

I get this error a lot when I have a VI with an XControl open and try to unlock the xcontrol to edit it.

Any way to get rid of it?  Explanations for it?

Thanks

[Andy_C.]

Hello Tim,

.cpp errors are internal crashes. If you post an example VI that can run on any computer and steps to reproduce the error in the latest version of LabVIEW then I can verify and pass it off to our R&D team for further analysis. Post it up and I'll see what I can find for you. Thanks!!

[elset191]

---

Andy C. wrote:

Hello Tim,

.cpp errors are internal crashes. If you post an example VI that can run on any computer and steps to reproduce the error in the latest version of LabVIEW then I can verify and pass it off to our R&D team for further analysis. Post it up and I'll see what I can find for you. Thanks!!

---

I don't have the latest version of LabVIEW (I run 8.6.1f1), but here is a VI and the XControl just in case it helps any.  

Steps to crash:

Open the VI

Open the XControl

Choose Unlock Library for Editing

This is where it crashes, if it crashes.  It doesn't happen all the time.  

[Andy_C.]

Hello Tim,

Are you having similar issue with other XControl? I cannot replicate the issue with LabVIEW 2009.

[elset191]

The only other XControl I have access to is the shipping example.  I haven't seen this error with that control.

I haven't written any other XControls, so I really can't say.

[Andy_C.]

Hello Tim,

We can try other XControls that are available on NI's community site (http://decibel.ni.com/content/search.jspa?resultTypes=BLOG_POST&resultTypes=DOCUMENT&resultTypes=MES...)

It seems that you are only having problem with that specific XCtonrol. Is that a XControl that you made? We can try to resave/mass compile the project for XControl to see if that would resolve the issue.

[elset191]

I tried some XControls from that search and I had no errors.  I mass compiled my XControl and tried again, the error still occurs. 

It ocurred to me that the error might be because my XControl is on a network, and may have been open on another computer.  So, I tested this with one of the other XControls I tried, but had no issues with that.