Re: Again: Temp user directory
From: Rob Kennedy (me3_at_privacy.net)
Date: 09/30/04
- Next message: Tom de Neef: "Re: Again: Temp user directory"
- Previous message: Martin Harvey (Demon account): "Re: Strange access violations"
- In reply to: Jamie: "Re: Again: Temp user directory"
- Next in thread: Jamie: "Re: Again: Temp user directory"
- Reply: Jamie: "Re: Again: Temp user directory"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 30 Sep 2004 12:52:55 -0500
Jamie wrote:
> whats wrong with GetFullPathName ?
GetFullPathName is a function for converting a relative path into a full
path. It merges the given relative path with the path to the current
directory. There is no indication that GetFullPathName would convert a
short path into a long path. In fact, the documentation specifically
denies that behavior. Allow me to quote from MSDN:
"GetFullPathName does no conversion of the specified file name,
lpFileName. If the specified file name exists, you can use
GetLongPathName and GetShortPathName to convert to long and short path
names, respectively."
If the OS you're targeting doesn't have GetLongPathName, then
GetFullPathName may be the first step in emulating its behavior. If you
have the Platform SDK, look in NewAPIs.h to see how Microsoft makes
GetLongPathName available to programs running Windows 95 and Windows NT.
> i think it would save the time of importing another
> API that is not already.
How much time will you save by not importing an API function?
-- Rob
- Next message: Tom de Neef: "Re: Again: Temp user directory"
- Previous message: Martin Harvey (Demon account): "Re: Strange access violations"
- In reply to: Jamie: "Re: Again: Temp user directory"
- Next in thread: Jamie: "Re: Again: Temp user directory"
- Reply: Jamie: "Re: Again: Temp user directory"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]