LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Radio Button bug

When converting my code from LV2011 to LV2012 SP1 I have the following weird phenomenon:

 

A Radio Button with option 1 and 2 visible inside a visible border - with AutoSizing set to "None" converts to the same size/location Radio Button with options 2 and 3 visible.  Since I could not find any mention of bugs in Radio Buttons the past few years my guess is that this bug is unknown and still present in the latest version of Labview.

 

Could someone verify?

0 Kudos
Message 1 of 3
(2,410 Views)

Hello Ettepet,

 

Could you clarify the behavior you're seeing?

 

Based on your description, it sounds like the following:

 

You have a radio button cluster (control) that contains three buttons.  You have set some of these buttons to be invisible via the "visible" property node.  When you upgrade the VI from LabVIEW 2011 to 2012 SP1, the buttons that are visible/invisible change. 

 

Do you have a VI that demonstrates this behavior when upgraded that you could share?

 

Regards,

Tom L.
0 Kudos
Message 2 of 3
(2,408 Views)

@0utlaw wrote:

Hello Ettepet,

 

Could you clarify the behavior you're seeing?

 

Based on your description, it sounds like the following:

 

You have a radio button cluster (control) that contains three buttons.  You have set some of these buttons to be invisible via the "visible" property node.  When you upgrade the VI from LabVIEW 2011 to 2012 SP1, the buttons that are visible/invisible change. 

 

Do you have a VI that demonstrates this behavior when upgraded that you could share?

 

Regards,


Your summation is almost correct: several buttons are set to be "visible" but not all are shown because of the resized (=smaller) border.

 

However, I just found out that even though I had this error a number of times (converting the same, gradually updated source) I don't seem able to reproduce it at this moment.  It could be that some invisible property of the radio button was corrupted and that I 'accidentally' fixed it somehow.  I will get back to this topic when I find a way to reproduce the bug.

 

edit: Thanks for your reply! 😉

0 Kudos
Message 3 of 3
(2,386 Views)