XControl gets stuck on Property after build

[ChrisWeis]

Hi,

I develop in LabView 2019. I created an XControl which was working very well. As soon as I built my project using the XControl in a packed lib and executed the VI it seems that the XControl gets stuck at any propertynode which is referencing a property I wrote. It does not happen in Debugmode before creating the packed lib. I got it to work if I put all the XControl property vi to my built destination folder. If I trie to pack the XControl inside the paked lib of my project it does not solve the Problem. 

Does anyone have any suggestions how to face this or why this happens?
kind regards

chris 

[paul_cardinale]

Suggestion: Use zip, not 7z.

[ChrisWeis]

As requested.

[JÞB]

I'll let others do the "Net" work but, some searching will turn up a presentation by Darren Nattinger explaining certian "Deficiencies" in LabVIEW that can cause issues when mixing advanced features.

It advises against trying certain combinations and explains why with some suggested workarounds.  I recall that X-nodes and X-Controls do not pack into *.ppl files very well.

Kudos for the links for y'all with the mad Google skills 

[ChrisWeis]

So I did a quick google search but could not find te presentation you talked about. But what you ar basically sayying is that I just should not do what I did and find an other way?

[JÞB · Accepted solution]

---

@ChrisWeis wrote:

So I did a quick google search but could not find te presentation you talked about. But what you ar basically sayying is that I just should not do what I did and find an other way?

---

Not too surprising since I eventually found it asLudicrous ways to fix broken LabVIEW code 

[paul_a_cardinale]

I looked at your code.  Didn't see anything funky.

But you've made zero effort to clean up your VIs.  Why is that?

Also, you didn't edit the xctl icon flag.

[TheQ]

I have run into the exact problem you are seeing and, just as Darren’s presentation suggests, I have had problems with both XNodes and XControls when it comes to using them in Packed Project Libraries (PPLs). I would follow Darren’s suggestion and try to avoid using them them together.

So, I guess you have two choices. Give up on PPLs so you can use the XControl or give up on XControls so you can use PPLs. 

One option, as an alternative to XControls, is QControls. I created the QControl Toolkit due to the problems of XControls working with PPLs. You can find the toolkit on VIPM.io and there are lots of resources to help you get started. (There is also a link in my signature below.)

[paul_a_cardinale]

Try creating a pre-build action that opens (in the build context), the VI(s) containing the XControl(s).  Then unlock the XControl(s).  Also create a corresponding post-build action that closes the references opened in the pre-build action.

[ChrisWeis]

I am happy about any suggstion you might have that helps me understand what clean up codes means in you opinion. Except for the facade Vi I just used the standard layouts? So are you talking about the facade VI our should I clean up the others too?

As for the Icon flag, it is true, since I put it together as an example.