Tab control tabs and pages don't match

[kc64]

The executable bug demo...

[Ben]

HI kc,

You did not reply to my query re: STRICT vs non-strict type def.

I noticed your mehtods enums are saved as strict. Strict is useful when you want to to have a consitant look for GUI puposes (which is why I could understand using it for the tab control) but not for methods (actions).

I am curious if this bug is due to the strict type-def.

Just trying to help,

Ben

[kc64]

Ben-- Thank you for the friendly reminder. I meant to respond and got side-tracked. I am too novice to know the subtleties of whether a strict type def should or should not be used for methods. I have been doing it that way ever since I first started writing with AEs but did so because I found out that using Controls did not preserve instances across VIs. I actually tried this with both a strict type def and a plain type def and obtained the same result. Thanks.

[kc64]

In the absence of any suggestions to fix this issue and the recognition by at least one other user that it is a bug, I am going to assume that NI needs to fix it and that there is presently no work-around.

[ColeTrain]

kc64,

I see that when I open the tab_demo.vi that tab 3 is selected and page 1 is displayed, however, by changing any one of the tabs and then setting that value as default, I cannot seem to reproduce what you originally posted.  What steps did you take to see this behavior?

[Ben]

Cole,

Are you using LV 8.6?

Try an earlier version to see the problem.

Ben

[ColeTrain]

I opened and saw everything with 8.5.1.  Again, I can see exactly what the problem is, I just cannot recreate it myself after setting default values and without being able to come up with any steps to recreate it, it's hard to know what to fix. 😉

[Ben]

I believe the issue is realted to the tab being defined as a "STRICT type def".

Ben

[ColeTrain]

Thanks for pointing that out Ben.  I have duplicated the issue and will be filing a CAR.  I have made new projects for both 8.5.1 and 8.6.1 and verified the behavior for both versions.  kc64, the best work around I can offer at this point is to make sure you save your VI with the defaulted tab active. 

[kc64]

Thank you all for your help. I will try your suggestion. Also, thank you for filing a CAR on this issue.