🚀 go-pugleaf

"Rodolfo Frino - Stargate Software" <starcinema@eftel.com> wrote in message
news:3e7e5a97@newsgroups.borland.com...

> The global variable ApplicationDirectory will get you the
> applications directory, even if you use TOpenDialog or any
> other Win3.1 component from the component palette.

You have not paid much attenttion to anything that has been said before.
You **cannot** rely on that approach, as there are several external factors
that can alter the process's current working directly *on startup* before
your code ever gets a chance to start running.  Parsing the
TApplication::ExeName property (which uses GetModuleFileName() internally)
is the *only* reliable way to get the application's actual installation
directory regardless of what the process's current working directly is set
to, whether manually, implicitially via component, or by the OS itself.

Also, just as an unrelated side note, if you want to inject your own startup
code into the TApplication startup process, the official ways is to assign a
function pointer to the global InitProc variable, not replacing the calling
of TApplication::Initialize() itself with your own calling.
TApplication::Initialize() calls InitProc() internally if it is assigned an
actual function pointer:


    TProcedure OldInitProc;
    void __fastcall MyInitialize(void)
    {
        ...
        if( OldInitProc ) OldInitProc();
    }

    WINAPI WinMain(HINSTANCE, HINSTANCE, LPSTR, int)
    {
        try
        {
            OldInitProc = InitProc;
            InitProc = MyInitialize;

            Application->Initialize()
            ...


Gambit