Re: Getting a Ttab*** to show on start-up
- From: "Maarten Wiltink" <maarten@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 20:20:38 +0100
"Tom de Neef" <tdeneef@xxxxxxxx> wrote in message
news:43d8f0bd$0$11071$e4fe514c@xxxxxxxxxxxxxxxxx
> "Maarten Wiltink" <maarten@xxxxxxxxxxxxxxxxxx> schreef in bericht
> news:43d89110$0$11073$e4fe514c@xxxxxxxxxxxxxxxxx
[...]
>> Things that may look outside their own form need to wait until all
>> forms have initialised; I'd probably add a line to the project file.
>
> But where ? I hesitate to start things outside the message loop.
No reason to fear. The project file is source code like all other
source code. There is no magic.
Between the Application.CreateForm lines and the Application.Run line
is the exact spot where you know all forms have initialised but the
message loop hasn't started yet.
This should be rare, though. It means at least two forms are
interdependent. A sure sign of poor design. (Your translation form
probably merely needs to be _last_; a different requirement.)
Groetjes,
Maarten Wiltink
.
- References:
- Getting a Ttab*** to show on start-up
- From: Tom de Neef
- Re: Getting a Ttab*** to show on start-up
- From: Maarten Wiltink
- Re: Getting a Ttab*** to show on start-up
- From: Tom de Neef
- Getting a Ttab*** to show on start-up
- Prev by Date: Re: Getting a Ttab*** to show on start-up
- Next by Date: Re: fix for blinking data-aware controls?
- Previous by thread: Re: Getting a Ttab*** to show on start-up
- Next by thread: Re: Getting a Ttab*** to show on start-up
- Index(es):