Tab control tabs and pages don't match

[kc64]

I have a tab control with three tabs and pages. When I start LV8.5.1 and open my front panel, page 1 and tab 2 are active. When I run the VI, the configuration does not change. This means that I have to click tab 1 to resync the tabs with the pages but this causes an event which is processed by my event handler. I don't see any reason why this situation should occur and I consider it a bug in LV. Have any of you run into this or similar situation and what can be done to remedy it? Thanks.

[Ben]

Bug in LV or the developed code?

Post your code so we can help you with this Q.

Ben

[ColeTrain]

kc64,

To clarify what you're talking about, are you stating that when you start your VI you have tab 2 selected, but you are viewing page 1?  I am a little unsure as to what you are referring to and as Ben asked, I would like to see your code so that we can help you out.  Thanks.

[kc64]

Attached is a zip archive that shows the problem.

[tst]

I can't look at the code at the moment, but I have seen cases (in 7.0, haven't checked in newer versions) where sometimes the tab selectors would not update (e.g. when using a local variable to change the value of the tab control) and would make it seem as if you're looking at a different page than the one you're actually looking at. My workaround was to write the value into the tab control using the Value property.

[Ben]

This may have been a bug in LV 8.5.1 that was fixed in LV 8.6.

WHen I opend your demo in LV 8.6 but did NOT save it, the FP indicated that tab #3 was selected (this is based on the graphic being smooth to the third tab) but the text from the first tab page was visable. After saving it as LV 8.6 it looks normal.

Q: is setting the type def of the tab control to a type-def rather than a "strict type def a viable work-around for your app?

Ben

Message Edited by Ben on 02-12-2009 12:42 PM

Message Edited by Ben on 02-12-2009 12:44 PM

[PaulG.]

I would call it a bug. I've been annoyed by this as well, and I believe I first saw it in 8.20. And I still see it in v 8.6. I would try a workaround by poking a value into a property node or local variable when the vi inits.

[Ben]

---

PaulG. wrote:
I would call it a bug. I've been annoyed by this as well, and I believe I first saw it in 8.20. And I still see it in v 8.6. I would try a workaround by poking a value into a property node or local variable when the vi inits.

---

Hi Paul,

Once I saved it in LV 8.6 it seemed OK. What are you seeing that I am missing?

Curious,

Ben

[kc64]

To address the question of setting a value when the code is run, I placed some code into the VI that does just that. You can set the tab, read the tab, and it behaves as expected except that the tab does not change. If you select a different tab to initialize with, it works properly.

[kc64]

I've been having trouble posting attachments on this machine. I click Add Attachments and nothing happens. I tried rebooting Windows, using both FireFox and MSIE and have had no success. I was going to attach a demo that shows the executable doing its thing and the tab not matching the page. I'll go back to my desk and post the VI.