🚀 go-pugleaf

> > However, you mentioned and then posted (on my request)
> > an example that is completely irrelevant (and that you
> > wrongly thought it was relevant)
>
> It was not irrelvant.  It directly proved statements you questioned
> earlier - the VCL could and was altering the process's current directory
at
> runtime, and I gave two very specific tests that proved that.  The only
> change you made to the project was to call GetCurrentDirectory() once
(which
> even that was not 100% reliable), whereas I was calling it multiple times
to
> show that it was indeed being altered over and over at runtime.
>
> > since I can overcome any internal change to the current directory
> > done within the application via either an *unofficial*  or an
> > *official* start up code.
>
> By caching the value once at startup and reusing it instead of retrieving
it
> over and over, of course.  That's fine.  That was not the point of my
sample
> project, though.
>
> > Of course, I cannot overcome an external change
>
> There already is a proven and well-known way to overcome that 100%
reliably,
> but you don't seem willing to use it yourself.  Using Application->ExeName
> is always accurate regardless of any startup code used to spawn the
process,
> regardless of any internal or external changes to the process at startup
or
> at runtime.

Application->ExeName will always be accurate, agreed. At no point in time
I said that I am not willing to use it. I pointed out that by getting the
value of the
current directory at startup and storing it into a variable, (when no
external factors have altered this value previously) and reusing it instead
of using GerCurrentDirectory() over and over again, will overcome any calls
to
GetCurrentDirectory in your example. Clearly you didn't understand this
point
initially since you said

"You can't always rely on that, either, as other controls outside your
control, such as TOpenDialog and the FileCtrl controls under the Win3.1
palette, can (and usually do) change the current directory internally "

But the method I presented shows that these Win3.1 controls cannot change
the ApplicationDirectory value in the example I posted when
ApplicationDirectory
is set as I shown in the example.

Once again that shows me that you failed to understand this point , and
that's why
I made the modifications to your code so that I could explain it to you.

Rodolfo