🚀 go-pugleaf

"Oren Halvani" <NoSpam@fdtd.com> wrote in message
news:42fac82b@newsgroups.borland.com...

> thats right, i'm using the BCB3 on this machine...don't laugh :-)
>
> i will use a workaround directly via the API...

You don't need a workaround.  Just load the function dynamically via the
GetProcAddress() function:

    typedef DWORD WINAPI (*LPFN_GLPN)(LPCTSTR, LPTSTR, DWORD cchBuffer);

    #ifdef UNICODE
    #define szGetLongPathName    L"GetLongPathNameW"
    else
    #define szGetLongPathName    "GetLongPathNameW"
    #endif

    #if (__BORLANDC__ < 0x550)
    AnsiString __fastcall IncludeTrailingBackslash(const AnsiString &S)
    {
        if( !IsPathDelimiter(S, S.Length()) )
            return (S + "\\");
        return S;
    }
    #endif

    AnsiString __fastcall TfrmMainUnit::GetTempFile()
    {
        TCHAR TempDir[MAX_PATH + 1] = {0};
        GetTempPath(MAX_PATH, TempDir);

        HMODULE hKernel32 = GetModuleHandle(TEXT("KERNEL32"));
        LPFN_GLPN lpGetLongPathName = (LPFN_GLPN) GetProcAddress(hKernel32,
szGetLongPathName);
        if( lpGetLongPathName )
            lpGetLongPathName(TempDir, TempDir, ARRAYSIZE(TempDir));

        return IncludeTrailingBackslash(TempDir) + "ShowRecord-Tempfile";
    }


> by the way, when i'm including: <windows.h> which DLL's will
> be effected, will it be still standalone...? this is something that i
never
> understand, i mean if you want to use a specific function that is declared
> in the huge <windows.h> will your program will be depening on all
> those lib's and DLL's

It already is.  The entire Win32 API is implemented in DLLs that are shipped
with the OS.  Every application already implicitally links to USER32.DLL,
KERNEL32.DLL, and SHELL32.DLL.  Those three DLLs implement the bulk of the
API.


Gambit