Y Controls

[paul_cardinale]

Looks like no one is interested.

[Albert.Geven]

I missed your answer and had my grandchilderen for this weekend, So probably play with it tomorrow

[paul_cardinale]

I'm currently chasing a strange bug: Once a VI with a Y Control is in memory, it won't unload (until you exit LabVIEW).

[BertMcMahan]

I'd like to check it out but I don't have a ton of time to do a full "dive" into them.

Can you throw your demo video on Youtube? I bet you'll get more hits if people can get a feel for what they do and how they're functionally different from Q/X controls.

[GerdW]

Hi Paul,

don't hurry - also other stuff to do…

In a first test I followed all the steps in your description successfully.

Then I changed the facade.ctl (replace button by numeric control) while another VI with my "Y test control" was still open: LabVIEW crashed and vanished from screen.

After restarting LabVIEW the "try to recreate the last items" dialog popped up: hitting "recreate" again crashed LabVIEW. I had to choose "don't recreate last items" top open LabVIEW…

(Sorry for rather rough translations of that dialog button texts as I currently use a German LabVIEW version.)

[paul_cardinale]

---

@GerdW wrote:

Hi Paul,

don't hurry - also other stuff to do…

In a first test I followed all the steps in your description successfully.

Then I changed the facade.ctl (replace button by numeric control) while another VI with my "Y test control" was still open: LabVIEW crashed and vanished from screen.

After restarting LabVIEW the "try to recreate the last items" dialog popped up: hitting "recreate" again crashed LabVIEW. I had to choose "don't recreate last items" top open LabVIEW…

(Sorry for rather rough translations of that dialog button texts as I currently use a German LabVIEW version.)

---

Hmmm.  That doesn't happen for me (although I've made a number of changes trying to find out why owning VIs get stuck in memory (OK, I know it's because something is holding a ref to the VI.  But I haven't figured out what))

[paul_cardinale]

Here's the new improved version.  I'm still chasing bugs, but they're not as nasty.

[BertMcMahan]

Opening in 2018, it's looking for "XML Path to LV Path.vi". I can't load in my test Y control without telling it where that file is. Should that be included in Y Controls.zip?

[paul_cardinale]

---

@BertMcMahan wrote:

Opening in 2018, it's looking for "XML Path to LV Path.vi". I can't load in my test Y control without telling it where that file is. Should that be included in Y Controls.zip?

---

Oops.  Here's the fix.

[paul_cardinale]

I finally resolved the issue of things getting stuck in memory.

Throw away the old versions, throw away Y Controls that you made with them, and use this new version.