Comments by Olongdomango

Olongdomango 14-Feb-14 12:21pm View

My projects are only of a small scale, but I'll examine this approach for future work. Thanks again.

Olongdomango 14-Feb-14 12:16pm View

Yes, I understand that and I have already applied recursion to universally set all controls as visible initially. This is easier in my case because only around 10% of them must be subsequently hidden on program launch. I never needed to write code to initially make all controls visible before, because this was the default property assigned via the designer.

Olongdomango 14-Feb-14 11:16am View

Thank you for the interesting links.

Olongdomango 14-Feb-14 11:10am View

Thank you for your detailed answer. If discipline is observed, this solution provides a good way of keeping track of the visiibility of all control types and is straight-forward. The only drawback is that it must be applied to every single control, but I simplified this task somewhat by initially using a For loop to call SetVisibility to True for each control in Me.Controls (with recursion for children), and then explicitly hiding specific controls with subsequent calls to SetVisibility. This is still much faster than re-creating controls from scratch.

Olongdomango 14-Feb-14 9:50am View

Yes, and yet the VisibleChanges event can be invoked from another function that sets the Visible property of a control on a non-selected tab to True. The handler however still returns a Visible property of False unless the tab that contains the control is selected. Furthermore, there must be another setting that manages the Visible property to determine if a control should be made visible or remain hidden when its parent tab is selected. It appears though that such a setting is not accessible to the coder.

Olongdomango 13-Feb-14 22:12pm View

Sorry for not being clear.

Yes, I mean System.Windows.Forms.TabControl and the tabs contained therein are known as System.Windows.Forms.TabPage.

Olongdomango 13-Feb-14 22:09pm View

I need to keep track of hidden controls to determine the properties of other controls. I've tried data binding, but this doesn't work on hidden controls. Inheriting classes is ok, but I'm adding new functionality to an existing application and I'd rather not re-create the few hundred controls that would be affected! By 'custom property' I simply mean the creation of new properties in my own Class that would inherit an existing System.Windows.Forms.Control Class. It might be possible to use such properties to mirror the Visible property. I wouldn't be 'injecting' anything.

Comments by Olongdomango (Top 7 by date)