Invisible Tab Page Causes Controls to not Work Properly

[Gleichman]

This may sound like an obvious "Don't do that", but it was not easy to diagnose when it was accidentally implemented. If you make a Tab control page invisible and later programmatically switch to that page, it will become visible, but the controls on the page will not function correctly. No error is generated. Example attached.

[Blokk]

I see the same behaviour with LabVIEW 2016.

Same with LV2015 SP1.

[kosist90]

Good to know... Quite interesting - is it some kind of LabVIEW bug?

[RavensFan]

I don't think it is a bug, per se.  Just a "don't do that" has the OP had set.

You may have changed to that page and it "showed" it,  but technically you never made it visible.

[JÞB]

---

@kosist90 wrote:

Good to know... Quite interesting - is it some kind of LabVIEW bug?

---

 yeah, probably CAR 603092 install the f1 patch then let us know if it gets better.

the f2 patch is newly available too.

[Blokk]

---

@JÞB wrote:

---

@kosist90 wrote:

Good to know... Quite interesting - is it some kind of LabVIEW bug?

---

 yeah, probably CAR 603092 install the f1 patch then let us know if it gets better.

the f2 patch is newly available too.

---

LabVIEW f1 patch did not solve the issue. I did not find f2 patch, only for LV x64. Is there f2 for 32 bit LV 2016 to try?

edit: found it: http://www.ni.com/download/labview-development-system-2016/6543/en/ 

Testing...

Edit2:

f2 patch, same result, same behaviour. Anyway, this is a kind of corner case. And another reason why using a SubPanel instead of a TAB control is just a better way to program...

[RavensFan]

Jeff,

Your link points to an NI Test stand patch.  And I can't find that CAR# anywhere.

I have LV 16f2 installed.  The behavior is just as originally described.

[Blokk]

---

@RavensFan wrote:

Jeff,

Your link points to an NI Test stand patch.  And I can't find that CAR# anywhere.

I have LV 16f2 installed.  The behavior is just as originally described.

---

You were faster than my Edit2 🙂

[Gleichman]

Here's the correct link to the CAR https://www.ni.com/en/support/documentation/supplemental/16/labview-2016-patch-details.html.

603092

After rearranging the tabs in a tab control, LabVIEW has the potential to crash when running or saving that VI.

This isn't the same thing. LabVIEW doesn't crash. I've done some more testing and found the same behavior in LV2013

[Gleichman]

If this is only a programming error, I would expect LabVIEW to not open the tab and return an error. Making the tab visible, but not fully functional seems like a bug. In my example you can type directly into the numeric control and the value change is captured, but the increment/decrement buttons on the numeric control are non-functional.