FindFile but what about the absolute path?

[Zinthose]

I have no issues using FileFirstFile and it's evil step cousin FileFindNextFile.

But..

Has anyone figured out a way to get the path from the search handle or through some other tricks?

Assume I don't know what the user is giving me for the path but lets say for an example, "C:\Windows\Temp\*"

Now I don't know what the path is.. just the full search string provided.  Without what I feel is unnecessary path string manipulations, how can I get the path from the File Search if the search only returns ONLY the name and not the path? 

Yes, I know I could use _PathSplit but it seam overkill.

[BrewManNH]

How are you getting the input from the users?

[Zinthose]

How are you getting the input from the users?

It's a command line option for automation.  Comma delimited list for processing each one.
I'm still trying to work around the problem.. just was hoping to find a more elegant solution than what I fear I'll have to implement.

[l3ill]

try this:

_WinAPI_GetFullPathName ( $sFilePath )
 

[Zinthose]

try this:

_WinAPI_GetFullPathName ( $sFilePath )
 

Tested.. It only returns the same data fed into by the user "C:\Windows\Temp\*" = "C:\Windows\Temp\*"

[Zinthose]

Ideally I would like to feed the search handle into a function so I would return the current path it is searching.

Something like...

$hndFileFind = FileFindFirstFile("C:\Windows\Temp\*")

$searchPath = _FileFindGetWorkingDirectory($hndFileFind)
;--> $searchPath = "C:\Windows\Temp"

 

Edited November 18, 2015 by Zinthose

[Melba23]

Zinthose,

I am still trying to understand how you end up with the search handle alone without the associated path that created it. You speak of a "comma delimited list" on the command line - a list of what? The paths?

Help us to help you by explaining in considerably more detail what exactly you are doing and how you need to deal with this command line - otherwise we are not really able to offer much assistance.

M23