Best way to have a tabbed MDI application

[Mac via DotNetMonster.com]

Hi all,

As some of you would know from my previous posts that I am rewriting our Unix
based system into .Net with a MDI interface.

Recently I have added a tab control to the top of the MDI parent form that
will contain a tab page for each open MDI child form. It is only 24 pixels
high so all you see is the tabstrip. Then I only have to add a bit of code to
the "changed index" event of the tab control as well as the "on activate"
event for the child forms (which is actually done on a baseform which is
inherited by all the child forms) to ensure that if either a tab is clicked
or another child form is activated then the current child form and current
tab are in sync.

Nothing too complicated here, but I am currently tossing up whether to
actually do away with having MDI child forms and just create all the intended
child forms as user controls which when required are inserted onto a new tab
page. But I am unsure if this is going to create headaches for me in managing
tab pages rather than MDI child forms.

The problem I have with an MDI app is preventing the users from changing the
state of the child form - I would like to have it maximised all the time. Is
there way to prevent the control box in the upper right corner of the MDI
form from being displayed?

Anyway, it would be great if people could share their experiences on tabbed
MDI applications so I can be aware of any pitfalls before I make the decision.
tia,

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Jeff Jarrell]

Mac,

I did this and I thought it worked out pretty well. Use the tab control,
then instantiate each form setting its parent to the tab page. You take the
boder off, set the dock to fill and there you go.

something like this...
dim fObjSelector as frmObjectSelect or
fObjSelector = New frmObjectSelect or
fObjSelector.Fo rmBorderStyle = FormBorderStyle .None
fObjSelector.To pLevel = False
fObjSelector.Pa rent = Me.FromHandle(T abControl1.TabP ages(0).Handle)
fObjSelector.Do ck = DockStyle.Fill
fObjSelector.Sh ow()

jeff

"Mac via DotNetMonster.c om" <u9483@uwe> wrote in message
news:58803686cb c54@uwe...

Hi all,

As some of you would know from my previous posts that I am rewriting our
Unix
based system into .Net with a MDI interface.

Recently I have added a tab control to the top of the MDI parent form that
will contain a tab page for each open MDI child form. It is only 24 pixels
high so all you see is the tabstrip. Then I only have to add a bit of code
to
the "changed index" event of the tab control as well as the "on activate"
event for the child forms (which is actually done on a baseform which is
inherited by all the child forms) to ensure that if either a tab is
clicked
or another child form is activated then the current child form and current
tab are in sync.

Nothing too complicated here, but I am currently tossing up whether to
actually do away with having MDI child forms and just create all the
intended
child forms as user controls which when required are inserted onto a new
tab
page. But I am unsure if this is going to create headaches for me in
managing
tab pages rather than MDI child forms.

The problem I have with an MDI app is preventing the users from changing
the
state of the child form - I would like to have it maximised all the time.
Is
there way to prevent the control box in the upper right corner of the MDI
form from being displayed?

Anyway, it would be great if people could share their experiences on
tabbed
MDI applications so I can be aware of any pitfalls before I make the
decision.
tia,

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Cor Ligthert [MVP]]

Mac,

Go first sit on the chair of your user.

Imaging that are using word and instead of that it is a MDI application as
it is, you have extended it with a Tab control where in can be all your
documents that are open.

I become already confused if I have 4 mdi doc files open in Word direct on
my screen. While you want to hide them even in tabpages.

I hope that this gives you an idea.
To give an exact answer, it is in my opinion a MDI or a Tab page, not both.

For me is a technical nice solution is not always a good user solution.

Just my thought,

Cor
"Mac via DotNetMonster.c om" <u9483@uwe> schreef in bericht
news:58803686cb c54@uwe...

Hi all,

As some of you would know from my previous posts that I am rewriting our
Unix
based system into .Net with a MDI interface.

Recently I have added a tab control to the top of the MDI parent form that
will contain a tab page for each open MDI child form. It is only 24 pixels
high so all you see is the tabstrip. Then I only have to add a bit of code
to
the "changed index" event of the tab control as well as the "on activate"
event for the child forms (which is actually done on a baseform which is
inherited by all the child forms) to ensure that if either a tab is
clicked
or another child form is activated then the current child form and current
tab are in sync.

Nothing too complicated here, but I am currently tossing up whether to
actually do away with having MDI child forms and just create all the
intended
child forms as user controls which when required are inserted onto a new
tab
page. But I am unsure if this is going to create headaches for me in
managing
tab pages rather than MDI child forms.

The problem I have with an MDI app is preventing the users from changing
the
state of the child form - I would like to have it maximised all the time.
Is
there way to prevent the control box in the upper right corner of the MDI
form from being displayed?

Anyway, it would be great if people could share their experiences on
tabbed
MDI applications so I can be aware of any pitfalls before I make the
decision.
tia,

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Mac via DotNetMonster.com]

Hi Jeff,

I am having difficulty trying to reproduce your solution. If I understand
correctly, it appears as though you have a form which you are slotting in as
a tabpage, which means you don't actually set the MDIParent property of these
forms at all? Is this correct?

And your frmObjectSelect or is of type form? Also where exactly is this code
placed - in your container form? Even though I know they exist, I cannot
access the Me.Fromhandle property or the TopLevel property.

Can you give me some further info on how you got this solution going - I
really like the sound of it. It if it behaves like it I think it will, it
will overcome the issue I had (and Cor pointed out) of having a detached
tabcontrol and MDI forms.
regards,

Mac

Jeff Jarrell wrote:

Mac,

I did this and I thought it worked out pretty well. Use the tab control,
then instantiate each form setting its parent to the tab page. You take the
boder off, set the dock to fill and there you go.

something like this...
dim fObjSelector as frmObjectSelect or
fObjSelector = New frmObjectSelect or
fObjSelector.Fo rmBorderStyle = FormBorderStyle .None
fObjSelector.To pLevel = False
fObjSelector.Pa rent = Me.FromHandle(T abControl1.TabP ages(0).Handle)
fObjSelector.Do ck = DockStyle.Fill
fObjSelector.Sh ow()

jeff

Hi all,

[quoted text clipped - 37 lines]

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Mac via DotNetMonster.com]

Thanks for that Cor - I think I got your point (actually I kinda feel like
Neo after a visit to the Oracle - I need a cookie!! :)

My concerns with having a tabfolder with all the forms as tab pages rather
than an MDI was that I would lose all the functionality that goes with forms?
Is this something I shouldn't be concerned about? Also being able to merge
the menu of the child form into that of the MDI parent is something that is
going to be handy for us. Is there a way to get around this?

I suppose what I would like is the best of both worlds, but in the end I may
just have to choose. But this a decision I am kinds dreading having to make
as it will determine the whole make up of the application!!

How have you seen the tab setup work because I really think this is way I
want to go. Just having MDI forms I think is a bit "old" and the users cannot
see what all the screens are that they have opened. I suppose also with the
tab setup I am trying to reproduce something similar to how Lotus Note is
setup.

Any thoughts appreciated

Mac

Cor Ligthert [MVP] wrote:

Mac,

Go first sit on the chair of your user.

Imaging that are using word and instead of that it is a MDI application as
it is, you have extended it with a Tab control where in can be all your
documents that are open.

I become already confused if I have 4 mdi doc files open in Word direct on
my screen. While you want to hide them even in tabpages.

I hope that this gives you an idea.
To give an exact answer, it is in my opinion a MDI or a Tab page, not both.

For me is a technical nice solution is not always a good user solution.

Just my thought,

Cor

Hi all,

[quoted text clipped - 37 lines]

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Jeff Jarrell]

Mac,

You have a MainForm that has a tab control. You have more forms in the
project that you will instantiate and insert into each tab page (where the
tab page the owner of the form. Most likely you'd put the sample code into
the form load of the MainForm. Nothing is marked as special like MDI
parent.

The seven lines of code would occur for each form you insert (or you would
generalize this.

frmObjectSelect or is a form with controls and stuff on it. nothing special.

I have used this techique to on complex forms to split out complexity into a
number of smaller forms (so multiple developers can work on it) rather than
a single, big, complex, monolithic form.

If you are still having problems let me know and i will get extract a
working sample for you.

jeff

"Mac via DotNetMonster.c om" <u9483@uwe> wrote in message
news:588c6f2cb9 9f7@uwe...

Hi Jeff,

I am having difficulty trying to reproduce your solution. If I understand
correctly, it appears as though you have a form which you are slotting in
as
a tabpage, which means you don't actually set the MDIParent property of
these
forms at all? Is this correct?

And your frmObjectSelect or is of type form? Also where exactly is this
code
placed - in your container form? Even though I know they exist, I cannot
access the Me.Fromhandle property or the TopLevel property.

Can you give me some further info on how you got this solution going - I
really like the sound of it. It if it behaves like it I think it will, it
will overcome the issue I had (and Cor pointed out) of having a detached
tabcontrol and MDI forms.
regards,

Mac

Jeff Jarrell wrote:

Mac,

I did this and I thought it worked out pretty well. Use the tab control,
then instantiate each form setting its parent to the tab page. You take
the
boder off, set the dock to fill and there you go.

something like this...
dim fObjSelector as frmObjectSelect or
fObjSelector = New frmObjectSelect or
fObjSelector.Fo rmBorderStyle = FormBorderStyle .None
fObjSelector.To pLevel = False
fObjSelector.Pa rent =
Me.FromHandle(T abControl1.TabP ages(0).Handle)
fObjSelector.Do ck = DockStyle.Fill
fObjSelector.Sh ow()

jeff

Hi all,

[quoted text clipped - 37 lines]

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Mac via DotNetMonster.com]

Hi again Jeff,

Have managed to get further - I can access those properties, they just
weren't in the intellisense box. Don't quite understand that but I am not
going to worry about.

Will continue to play with it - getting an invalid index message at the
moment. Will let you know how I go.
Mac

Mac wrote:

Thanks for that Cor - I think I got your point (actually I kinda feel like
Neo after a visit to the Oracle - I need a cookie!! :)

My concerns with having a tabfolder with all the forms as tab pages rather
than an MDI was that I would lose all the functionality that goes with forms?
Is this something I shouldn't be concerned about? Also being able to merge
the menu of the child form into that of the MDI parent is something that is
going to be handy for us. Is there a way to get around this?

I suppose what I would like is the best of both worlds, but in the end I may
just have to choose. But this a decision I am kinds dreading having to make
as it will determine the whole make up of the application!!

How have you seen the tab setup work because I really think this is way I
want to go. Just having MDI forms I think is a bit "old" and the users cannot
see what all the screens are that they have opened. I suppose also with the
tab setup I am trying to reproduce something similar to how Lotus Note is
setup.

Any thoughts appreciated

Mac

Mac,

[quoted text clipped - 21 lines]

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Mac via DotNetMonster.com]

Jeff,

couldn't seem to get past the index error - "0 is not a valid value for
index". In an attempt to resolve it before the Me.FromHandle statement I
actually added a blank tabpage to the tab control.

The Me.FromHandle statement was then fine, but I then got an "object not
instantiated" error when I attempt myForm.show. I then tried a more basic
form and there was no error but the form doesn't actually show! So in the end
my workaround doesn't work, so I guess I am back to trying to fix the index
error. Do you have any suggestions? Do I need to do something to the
tabcontrol first before referencing it?
Mac

Mac wrote:

Hi again Jeff,

Have managed to get further - I can access those properties, they just
weren't in the intellisense box. Don't quite understand that but I am not
going to worry about.

Will continue to play with it - getting an invalid index message at the
moment. Will let you know how I go.

Mac

Thanks for that Cor - I think I got your point (actually I kinda feel like
Neo after a visit to the Oracle - I need a cookie!! :)

[quoted text clipped - 24 lines]

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Jeff Jarrell]

you do need to have (read insert) a blank tab page for each sub form you are
instantiating.

"Mac via DotNetMonster.c om" <u9483@uwe> wrote in message
news:588e33d3a9 ba7@uwe...

Jeff,

couldn't seem to get past the index error - "0 is not a valid value for
index". In an attempt to resolve it before the Me.FromHandle statement I
actually added a blank tabpage to the tab control.

The Me.FromHandle statement was then fine, but I then got an "object not
instantiated" error when I attempt myForm.show. I then tried a more basic
form and there was no error but the form doesn't actually show! So in the
end
my workaround doesn't work, so I guess I am back to trying to fix the
index
error. Do you have any suggestions? Do I need to do something to the
tabcontrol first before referencing it?
Mac

Mac wrote:

Hi again Jeff,

Have managed to get further - I can access those properties, they just
weren't in the intellisense box. Don't quite understand that but I am not
going to worry about.

Will continue to play with it - getting an invalid index message at the
moment. Will let you know how I go.

Mac

Thanks for that Cor - I think I got your point (actually I kinda feel
like
Neo after a visit to the Oracle - I need a cookie!! :)

[quoted text clipped - 24 lines]

>
> Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1

[Simon Verona]

Out of interest, I have done the same as Jeff in his answer, but instead of
using the tab control, I've used a toolbar and a panel.

What I do is respond to the click event of the toolbar, work out which
button has been selected and change it to "pressed" so the user can see
which is the active button and then set the mdiparent of the form in
question to the panel (after creating the form if necessary)... (you need to
switch the "toplevel" property of the form to false You can turn off the
control box and title for the form to make it appear "properly" (rather than
looking like a form on a panel!).

I'm presuming that you are not using mdi forms in the same way as word - ie
open multiple documents, but more as a way of breaking the functionality of
an application up ?

Just another way forward. I prefer it to the tabcontrol because you can
assign images easily to the buttons and have more control of the visuals...

You do still have the "menus" problems, but you could pretty easily merge
the menus if required in code..

Regards
Simon

"Mac via DotNetMonster.c om" <u9483@uwe> wrote in message
news:58803686cb c54@uwe...

Hi all,

As some of you would know from my previous posts that I am rewriting our
Unix
based system into .Net with a MDI interface.

Recently I have added a tab control to the top of the MDI parent form that
will contain a tab page for each open MDI child form. It is only 24 pixels
high so all you see is the tabstrip. Then I only have to add a bit of code
to
the "changed index" event of the tab control as well as the "on activate"
event for the child forms (which is actually done on a baseform which is
inherited by all the child forms) to ensure that if either a tab is
clicked
or another child form is activated then the current child form and current
tab are in sync.

Nothing too complicated here, but I am currently tossing up whether to
actually do away with having MDI child forms and just create all the
intended
child forms as user controls which when required are inserted onto a new
tab
page. But I am unsure if this is going to create headaches for me in
managing
tab pages rather than MDI child forms.

The problem I have with an MDI app is preventing the users from changing
the
state of the child form - I would like to have it maximised all the time.
Is
there way to prevent the control box in the upper right corner of the MDI
form from being displayed?

Anyway, it would be great if people could share their experiences on
tabbed
MDI applications so I can be aware of any pitfalls before I make the
decision.
tia,

Mac

--
Message posted via DotNetMonster.c om
http://www.dotnetmonster.com/Uwe/For...b-net/200512/1