🚀 go-pugleaf

Hans Galema <notused@notused.nl> wrote:

>Why ? Please show the code where you load the DLL.

The code is this:



There.

Seriously - to get the program to use a resource DLL, you create a DLL,
you give it the relevant file extension (e.g. ENG for English GB, ENU
for English US, etc.), and you place it in the same directory as the
executable. You do not write any code (not in the loading executable,
anyway - you may want a stub DLL entry point in the DLL). You do not
change any settings. It just does it.

The downside of this is that the Borland-supplied code does the
following:

a) Finds own name
b) Removes file extension (OCX, DLL, EXE, whatever)
c) Finds locale code (ENG, whatever)
d) Appends locale code to base name and attempt to load DLL
e) If failed, tries with shortened locale name (e.g. EN)
f) If failed, uses resources internal to original executable.

It's nicely automatic, but I know of no way to tell it to go look in a
different directory - though why you would want to, I'm not sure. I can
see ways to switch which resource DLL is used on the fly, but not where
to go for them.

Alan Bellingham
Chief Software Developer
-- 
Tel: +44 (0) 1763 248866
Fax: +44 (0) 1763 246000
Email: alanb@episys.com
Web: www.episys.com
UK Office: Episys Ltd, Newark Close, Royston, Hertfordshire, SG8 5HL, UK
North America Office: Episys, 200 South Wacker Drive, Suite 3100,
Chicago, IL 60606, USA