CODEWITHSUNDEEP
c#.netwindows
Peter Olsson
Peter Olsson

Reputation: 1322

Building C# .NET windows application with multiple views

I'm rewriting an old application and use this as a good opportunity to try out C# and .NET development (I usually do a lot of plug-in stuff in C).

The application is basically a timer collecting data. It has a start view with a button to start the measurement. During the measurement the app has five different views depending on what information the user wants to see.

What is the best practice to switch between the views? From start to running? Between the running views?

Ideas:

Upvotes: 11

Views: 21159

Answers (5)

Hath
Hath

Reputation: 12779

What I do is to have a Panel where your different views will sit on the main form. then create user controls for your different views.

Then when I want to switch between a'view' you dock it to Panel on the main form.. code looks a little like this.

i preffer this because you can then reuse your views, like if you want to open up a view in a tab you can dock your user controls inside tab pages.. or even inherit from tabpage instead of usercontrol to make things a bit more generic

public partial class MainForm : Form
{
    public enum FormViews
    {
        A, B
    }
    private MyViewA viewA; //user control with view a on it 
    private MyViewB viewB; //user control with view b on it

    private FormViews _formView;
    public FormViews FormView
    {
        get
        {
            return _formView;
        }
        set
        {
            _formView = value;
            OnFormViewChanged(_formView);
        }
    }
    protected virtual void OnFormViewChanged(FormViews view)
    {
        //contentPanel is just a System.Windows.Forms.Panel docked to fill the form
        switch (view)
        {
            case FormViews.A:
                if (viewA != null) viewA = new MyViewA();
                //extension method, you could use a static function.
                this.contentPanel.DockControl(viewA); 
                break;
            case FormViews.B:
                if (viewB != null) viewB = new MyViewB();
                this.contentPanel.DockControl(viewB);
                break;
        }
    }

    public MainForm()
    {

        InitializeComponent();
        FormView = FormViews.A; //simply change views like this
    }
}

public static class PanelExtensions
{
    public static void DockControl(this Panel thisControl, Control controlToDock)
    {
        thisControl.Controls.Clear();
        thisControl.Controls.Add(controlToDock);
        controlToDock.Dock = DockStyle.Fill;
    }
}

Upvotes: 7

ArielBH
ArielBH

Reputation: 2001

I would also check out Composite Application Guidance for WPF or Smart Client Software Factory

Upvotes: 0

Chris Karcher
Chris Karcher

Reputation: 2292

Creating a bunch of overlaid panels is a design-time nightmare.

I would suggest using a tab control with each "view" on a separate tab, and then picking the correct tab at runtime. You can avoid showing the tab headers by putting something like this in your form's Load event:

tabControl1.Top = tabControl1.Top - tabControl1.ItemSize.Height;
tabControl1.Height = tabControl1.Height + tabControl1.ItemSize.Height;
tabControl1.Region = new Region(new RectangleF(tabPage1.Left, tabPage1.Top, tabPage1.Width, tabPage1.Height + tabControl1.ItemSize.Height));

Upvotes: 8

Brian Ensink
Brian Ensink

Reputation: 11218

The method I often use is actually to pre-setup all my controls on individual "Panel" controls and then show and hide these panels as I need them.

Instead of making each view a panel within a single form you could make each view a UserControl. Then create a single form and write code to create and display the correct UserControl in the Form and to switch from one to the next. This would be easier to maintain because you will have a separate class for each view instead of a single Form class with 6 panels each with their own controls -- that seems difficult and error prone to maintain.

Upvotes: 1

Adam Haile
Adam Haile

Reputation: 31349

Tabbed forms are usually good... but only if you want the user to be able to see any view at any time... and it sounds like you might not.

Separate forms definitely works, but you need to make sure that the switch is seemless...if you make sure the new form appears the same exact size and location of the old form, it will look like it thew same for with changing controls.

The method I often use is actually to pre-setup all my controls on individual "Panel" controls and then show and hide these panels as I need them. The "Panel" control is basically a control container... you can move the panel and all controls on it move relative. And if you show or hide the panel, the controls on it do the same. They are great for situations like this.

Upvotes: 3

Related Questions