Multi-Form Application Design Issues

  • Thread starter Thread starter jd_ie
  • Start date Start date
J

jd_ie

Hi all,

I have an application with multiple forms. I have one form setup as the
startup form, so that this is the first form shown when the
applications starts. Whenever I leave this form, I simply hide it and
pass a reference to it to the next form I show. I do not close the
startup form as this seems to close the application.

Whenever the application moves between any of the other forms, I close
(not hide) the currently shown form after showing the new form, so that
I never have for more than a short time more than two forms loaded (the
hidden startup form and the current form). I always pass a reference to
the hidden startup form to every form shown so that whenever I need to
show the startup form again, I use the reference to unhide it, and then
I close the curent form.

Is this a good/bad way to program/structure the application? It's my
first application. It seems to work well, but is there a better way to
do it, for future reference?

Thanks all,

Regards,

Jonathan
 
Hi

This is an often asked question and in my opinion it depends on what
you actually want to achieve!
For example with .net cf 1.0 (so SP) I had the problem that loading a
Form
took quite a time so I had to cache it (load it when the app started)

Here is for example a solution to this topic from opennetcf
http://www.opennetcf.org/Articles/IStack.asp
This one references to the following
http://msdn.microsoft.com/mobility/...ary/en-us/dnnetcomp/html/netcfuiframework.asp

But from my point of view:
Never change a running System NEVER EVER ;-)

Norbert
 
Thanks for the reply Norbert!

Would you mind telling me, what do you mean when you say:

Never change a running System NEVER EVER?

You mean if it is working satisfactorily, then don't change it?
 
Yes
If its working for you and your custumer
why put several more days work in it?!?

Norbert
 
Back
Top