Organizing Windows Form UI Components at Design Time


C

curtis.johnstone

I am designing a UI with Windows Forms and C#. The main part of the UI
(in the center) is context sensitive - it changes based on the user
selections in the navigation bar on the left hand side - the
appropriate center UI elements are made visible or hidden based on the
user selection.

That 'center area' is now very cluttered at design time (in the visual
designer). What is a good technique to avoid this? I would like to use
a tab control and then just hide the actual tabs, but there is no
property on the native tab control to do this...

What is the standard practice for doing this at design time?

Thanks,
Curtis
 
Ad

Advertisements

H

Herfried K. Wagner [MVP]

I am designing a UI with Windows Forms and C#. The main part of the UI
(in the center) is context sensitive - it changes based on the user
selections in the navigation bar on the left hand side - the
appropriate center UI elements are made visible or hidden based on the
user selection.

That 'center area' is now very cluttered at design time (in the visual
designer). What is a good technique to avoid this? I would like to use
a tab control and then just hide the actual tabs, but there is no
property on the native tab control to do this...
You may want to use user controls ("Project" -> "Add user control...") for
the different "views".
 
C

Curtis

Thanks - that helps. This allows me to design each seperate context
sensitive 'center piece' as an individual component. I still like the
tab-control-type solution so all the UI pieces appear at design time
where they will be show up at run time, but this will suffice.
 
H

Herfried K. Wagner [MVP]

Curtis said:
Thanks - that helps. This allows me to design each seperate context
sensitive 'center piece' as an individual component. I still like the
tab-control-type solution so all the UI pieces appear at design time
where they will be show up at run time, but this will suffice.
Removing a tabcontrol's tabpage headers
<URL:http://dotnet.mvps.org/dotnet/faqs/?id=tabcontrolremoveheaders&lang=en>

IIRC this doesn't disable keyboard navigation between the tabs.
 
C

Curtis

Thanks - a bit of hack, but it works. I am surprised they just didn't
support this in the .NET control - maybe it's coming.

I am finding the seperate User Control will promote a cleaner
design....
 
Ad

Advertisements

Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top