 |
Desktop Development »
Tabs & Property Pages »
Tabs and Property Pages
Intermediate
Magic TabControl - VS.NET StyleBy Phil WrightAn article on tab controls |
C#, Windows, .NET 1.0, Dev
|
|
Advanced Search |
|
|
|
||||||||||||||||
TabControl Sample contains a Form with a
TabControl instance that allows the various properties of the TabControl to be
experimented with. The source code for the actual control is inside the
separate second download. At nearly 1MB in size, I thought people would prefer
to download the sample before deciding if they want to install the entire
source code project!
TabControl is used to manage a collection of TabPage instances
which themselves are used to describe an individual page. Only a single page
can be displayed at any time and a row of tabs are shown to allow the user to
select between the available pages.
TabControl instance along with its TabPage
instances. First you will need to add the control to the toolbox by
right-clicking the toolbox window and selecting the customize option. Navigate
to the appropriate directory and select the Magic Library DLL. The toolbox will
now list the extra controls that are exposed by the library including the TabControl.
Drag and drop a new instance onto your Form and select the TabPages
property.
This will cause a dialog to appear that allows the creation and removal of
pages to the control instance. It also allows you to modify the properties for
each page added. Dismiss this dialog and you can now click on the control tabs
in order to select the page you want to configure. As the TabPage class
is derived from the Panel class you can now drag and drop other controls
onto the page as desired. The designer will automatically generate the code
needed to cause this configuration to be persisted as code in your Form.
TabControl exposes a property called TabPages that allows the
developer to add, remove and modify pages displayed by the control. Use the
standard methods to modify this collection as you would with any of the
framework collections.
Here is an example that shows the collection being manipulated: -
Crownwood.Magic.Controls.TabControl tab =
new Crownwood.Magic.Controls.TabControl();
Crownwood.Magic.Controls.TabPage tabPage1 =
new Crownwood.Magic.Controls.TabPage();
Crownwood.Magic.Controls.TabPage tabPage2 =
new Crownwood.Magic.Controls.TabPage();
// Add a range of pages to the collection
tab.TabPages.AddRange(new TabPage[] pages{
tabPage1, tabPage2});
// Remove all the contents
tab.TabPages.Clear();
// Add a single entry
tab.TabPages.Add(tabPage1);
// Insert a single entry at a given position
tab.TabPages.Insert(0, tabPage2);
// Use index accessor for retrieving a page
// reference
Console.WriteLine("TabPages[0] name = {0}",
tab.TabPages[0].Text);
// Test if the collection contains an entry
Console.WriteLine("Contains tabPage1 = {0}",
tab.TabPages.Contains(tabPage1));
// Gain access to a Page by its Title
Console.WriteLine("Contains a named page? {0}",
tab.TabPages["Page1"] != null);
// Remove by object reference
tab.TabPages.Remove(tabPage1);
// Remove by index
tab.TabPages.RemoveAt(0);
Appearance which, as the
name suggests, is used to define the appearance of the control. When the value
of this property is changed it will automatically alter the values of other
properties to the defaults for the defined appearance. Therefore this is the
first property to be set otherwise previous changes to other properties will be
overwritten once this is set.
The three possible values for the property are VisualAppearance.MultiDocument,
VisualAppearance.MultiForm and VisualAppearance.MultiBox. The
first of these will place the page tabs at the top of the control and show both
arrow and close buttons. An example use of this would be to control which of a
group of documents is displayed. For example, use this appearance to achieve
the same effect as the Visual Studio .NET control that contains the open
documents.
The second appearance VisualAppearance.MultiForm places the page tabs at
the bottom of the control and does not show any buttons. Instead all the tabs
are sized to fit within whatever width the control is defined as. Use this
appearance to mimic the style of tab control seen in Visual Studio .NET inside
docking windows.
Use the third appearance VisualAppearance.MultiBox to create the high
contrast appearance you get when editing an HTML document in Visual Studio
.NET, where the document has two options at the bottom of the window.
Once the appearance has been set the developer can still modify the other
properties to alter the exact look and feel wanted. For example, the PositionTop
property could be used to shift the default position of the tabs for the MultiForm
appearance from the bottom of the control to the top. Use the supplied sample
project to experiment and achieve the look required.
TabControl
but only two are of interest to most developers. These are the ClosePressed
event that gets fired when the user presses the close button, and SelectionChanged
which notifies a change in the current selection.
To see how to hook into these events see the following code: -
public void SomeMethod()
{
Crownwood.Magic.Controls.TabControl tab =
new Crownwood.Magic.Controls.TabControl();
tab.ClosePressed += new EventHandler(
OnClosePressed);
tab.SelectionChanged += new EventHandler(
OnSelectionChanged);
...
}
protected void OnClosePressed(object sender,
EventArgs e)
{
Console.WriteLine("OnClosePressed");
}
protected void OnSelectionChanged(object sender,
EventArgs e)
{
Crownwood.Magic.Controls.TabControl tab =
(Crownwood.Magic.Controls.TabControl)sender;
Console.WriteLine("New selection = {0}",
tab.SelectedIndex);
}
Multiline property to get a multi lines display
of tabs which you will not see in the VS.NET version. Another interesting feature is the HideTabsMode
property. You can use this to decide when the tabs area is made visible/invisible. For example, you can have
the tabs hidden unless the mouse is hovering over the control. Check out the sample to play around with this
and the other available options.
30 Sept 2002 - Initial Revision
General 
News 
Question 
Answer 
Joke 
Rant 
Admin
|
PermaLink |
Privacy |
Terms of Use
Last Updated: 29 Sep 2002 Editor: Brian Delahunty |
Copyright 2002 by Phil Wright Everything else Copyright © CodeProject, 1999-2009 Web11 | Advertise on the Code Project |
Over-worked, under-paid, glorified "secretary". 
