LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"Unbundle Refs By Name" Xnode


@paul_cardinale wrote:

wiebe@CARYA wrote:

I wired a reference to a cluster with 2 elements and no labels. Added labels. LabVIEW hangs. (AdaptToInputs.vi I think).


I couldn't get that to happen.


1) create an empty cluster constant.

2) drop a 1st numeric constant in it (no label).

3) drop a 2nd numeric constant in it (no label).

4) change to control.

5) create reference.

6) wire reference to xnode.

7) extract the xnode (to show 2 outputs).

😎 give 1st numeric control a label ("a").

9) give 2st numeric control a label ("b").

 

Step 9 hangs LabVIEW for me (18 and 20).

 

EDIT: the 😎 is free.

0 Kudos
Message 11 of 16
(225 Views)

wiebe@CARYA wrote:

@paul_cardinale wrote:

wiebe@CARYA wrote:

I wired a reference to a cluster with 2 elements and no labels. Added labels. LabVIEW hangs. (AdaptToInputs.vi I think).


I couldn't get that to happen.


1) create an empty cluster constant.

2) drop a 1st numeric constant in it (no label).

3) drop a 2nd numeric constant in it (no label).

4) change to control.

5) create reference.

6) wire reference to xnode.

7) extract the xnode (to show 2 outputs).

😎 give 1st numeric control a label ("a").

9) give 2st numeric control a label ("b").

 

Step 9 hangs LabVIEW for me (18 and 20).

 

EDIT: the 😎 is free.


It's the same when the labels are the same, not just empty.

 

So, if two controls are labeled "a", renaming the first to "b" and the 2nd to "c", LV hangs too.

 

Probably the while loop in AdaptToInputs.

0 Kudos
Message 12 of 16
(218 Views)

Also tried to get elements from clusters that come from an array.

 

This broke the VI.

 

I tried to insert a " To More Specific", but that hangs LV.

Hanging XNode.PNG

0 Kudos
Message 13 of 16
(210 Views)

Here's the fixed up version.

  • Better Error messaging
  • When to break wires or VI
  • Fixed LV Hang bug
  • Elements 1 Pixel bigger
  • Smarter about elements with same name or empty name
"If you weren't supposed to push it, it wouldn't be a button."
Message 14 of 16
(193 Views)

Here's wild bug: I have a cluster in a cluster and I want to get a reference to an item in the inner cluster; so I daisy-chain the XNode.

When I do that in LV 2018, the wire breaks:

lv18-1.png

 

However in LV 2019, it works OK:

lv19.png

 

Then if I take that LV 2019 version and save it as LV 2018, and open it in LV 2018, it's OK:

lv18-2.png

 

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 15 of 16
(84 Views)

If you sprinkle in some Always Copies does that help?  I mean it may help but it doesn't really help, unless it also gets fixed by putting an always copy in the generated code.

 

Edit: I also just tested this in 2018 SP1 with a non-typed cluster, and a type def in a type def and they both worked without a broken wire.

0 Kudos
Message 16 of 16
(73 Views)