Glen
My reasons are like that.
I may have different types of user interface for the same application. Say I
have girls inteface with lots of flowers on screen,boys interface with guns
and motorcicles and old blokes (like me) interface with fishing/golf gear
flying around.
It is a bit more complex than this but it does not matter.
I have base class for the form which is used for interaction with the user.
All standard functionality is built into it. All end user interface forms
for girls and boys are derived from that class and inherit its
functionality.
Say at start up user gets prompted : "Girl,Boy or Old man ?' , then correct
UI form implementation is being chosen, created and shown. Main form is not
needed any longer.
To do it the other way around as you suggest does not seem to be possible.
Thanks anyway
Alex
----- Original Message -----
From: "Glen Boyd" <[EMAIL PROTECTED]>
To: "Multiple recipients of list delphi" <[EMAIL PROTECTED]>
Sent: Monday, 12 June 2000 14:41
Subject: Re: [DUG]: Changing main form at run-time
> Alex Kouznetsov wrote:
> > I have tried hiding base main application form and letting the user to
> > interact with secondary form as if it was an application main form.
> > Unfortunately this way I get lots of little annoying problems with
> > application activating, minimizing,restoring etc.
>
> Why go to great lengths to hide the main form? It would be much easier
> to have a secondary form that asks for the information that then closes
> and passes control back to the main form.
>
> --
> Glen Boyd <[EMAIL PROTECTED]>
> Programmer Napier City Council
> Private Bag 6010, Napier, NEW ZEALAND
> Phone: +64-6-8357579 Fax: +64-6-8357574
> --------------------------------------------------------------------------
-
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
