Tab control enum to be typedef rather than plain enum

[Neil.Pate]

Another suggestion, which would be nice.

When you have a tab control and create an enum from it to use in the BD, it is not dynamically linked to the original tab control. In other words if you add or remove a page the enum on the BD is not valid anymore, but is not actually broken as its just a plain vanilla enum.

If the enum created from a tab control was a typedef then it would automatically update if the tab pages are modified.

A work around is to have the tab control as a typedef itself (actually I have just thought of this, don't know why it never occurred to me before!) but I would still like the modified behaviour as its one less typedef I have to manage myself!

<INSERT FANCY PICTURE HERE TO GET EVERYONE'S ATTENTION>

[X.]

the alternative option described by nrp is buggy, as discussed here, so in practice, it is NOT an option. I think I would prefer to have the original suggestion working.

[AG@Amfax]

I am in complete agreement with nrp and X, when a Tab Control is changed to a a strict type def surely the enum control should also be!! I would strongly advise this to be implmented in future versions of LV as it can be a real pain!! A further suggestion would be to allow for other controls to be placed within the pages of your custom control tab, as I have found that removing and reodering pages within my typedef tab can cause real problems in the code (especially as im programatically changing tabs using events)!