Hello
obfusc88I just had a few more thoughts of help for you if you try to make all elements invisible on a TabPage.
1. Remember to also make static text, boxes, and lines Invisible, not necessary, but makes a much cleaner picture, especially when combined with my next thought.
2. Change the label on the TabPage to make it empty. This will shrink the width of the Tab on the bottom to a very small area, (almost invisible). Now if someone clicks on that Tab by mistake, they will see a totally blank page because you did step 1, removed ALL elements, not just data elements.
Here is the code to change the label:
IF TurnOffTabPage = TRUE Then {
LABEL(tabPage0,"")
VISIBILITY(Element1,0)
VISIBILITY(Element2,0)
VISIBILITY(Element3,0)
>
>
>
VISIBILITY(Element99,0)
}
IF TurnOffTabPage = FALSE Then {
LABEL(tabPage0," Original Tab Label ")
VISIBILITY(Element1,1)
VISIBILITY(Element2,1)
VISIBILITY(Element3,1)
>
>
>
VISIBILITY(Element99,1)
}
IF you don't think there would be a confilct with various labels on the Tabs, you could capture the current Label value and save it as a global variable, then use that global variable later when you need to restore the name of the label. That wpuld make this more generic, and the value of the label would not be hardcoded. But that is probably not useful if you are manually entering the element names to be toggled anyway.

Hmm, that raises a new question....It should be possible to use a loop to make many elements VISIBLE, or READONLY, etc. but how can we identify the parent element of the data elements? For instance, I don't think we can know that a particular element is on a TabGroup on ANY TabPage, nevermind knowing which specific TabPage it might be on. Any chance that the magical Version 2 will provide this capability ..the ability to ID the parent that all elements are attached to? We now can see parenting when we move elements, so the logic is there under the covers somewhere. This is the type of thing that
Mark usually whips out right away. Go for it
Mark