[Win32] FindFirstFile - FindNextFile returning name of directory

[Win32] FindFirstFile - FindNextFile returning name of directory

North~

Member #12,192

August 2010

I'm trying to find all the files in a directory named "en" and no matter how many times I search through with FindNextFile, it always returns the same thing. "en" which is not a file or directory inside of \en. Anyone see a problem?

#SelectExpand
  1if (!isADirectory(argv[1]))
      {
          printf("%s is not a directory.",argv[1]);
          exit(1);
      }
      else
      {
          printf("%s is a directory.\n",argv[1]);
      }
      
      WIN32_FIND_DATA wData;
      HANDLE wHandle;
 13
      wHandle = FindFirstFile(argv[1],&wData);
 15
      printf("First file in directory is: %s\n",wData.cFileName);
 17
      if (wHandle == INVALID_HANDLE_VALUE)
      {
          printf("Error in finding a directory.");
      }
 22
      FindNextFile(wHandle, &wData);
      printf("Second file in directory is: %s\n",wData.cFileName);
      FindNextFile(wHandle, &wData);
      printf("Third file in directory is: %s\n",wData.cFileName);
 27
      string fullpath_s = argv[1];
      fullpath_s += "\\";
      fullpath_s += wData.cFileName;

--------------------------------------------------
http://blog.wolfire.com/2009/04/always-initialize-your-memory/

If this is possible if you don't correctly initialize memory, it should be a priority of the highest order.

Edgar Reynaldo

Major Reynaldo

May 2007

From looking at
FindFirstFile
FindNextFile
WIN32_FIND_DATA
it seems you are using the functions properly.

So, that leaves the problem up to the path you are passing into your code as argv[1].

According to the docs, it seems you should be using a path like this :

drive:\\folder\\en*

Eagle and Allegro 5 binaries | Older Allegro 4 and 5 binaries | Allegro 5 compile guide
King Piccolo will make it so Then I could just flip it with some sweet, sweet matrix math. In either case, I’ll ride this wagon until the wheels fall off. Thanks to those that keep it running

North~

Member #12,192

August 2010

I have tried this before with single and double backspaces and the result is the same

First file: en
Second file: en
Third file: en

I am aware that the first two things in a folder are references to the folder itself "." and the parent ".." but even if it was picking up these, the second "file" should be "Desktop" and the third should be the first file in the actual folder. However, this is not the case, and I am confused.

--------------------------------------------------
http://blog.wolfire.com/2009/04/always-initialize-your-memory/

If this is possible if you don't correctly initialize memory, it should be a priority of the highest order.

Edgar Reynaldo

Major Reynaldo

May 2007

North~ said:

I misread what you said earlier. I thought you were looking for all the files starting with 'en', not for all the files in a directory named 'en'. You need to alter your search path to something like this :

drive:\\folder\\en\\*

(Only escape the backslashes if you aren't entering it in manually)

I assume before you were trying to search by using something like this :

drive:\\folder\\en

and that would only find the en folder, which is why it keeps showing up when you call FindNextFile.

Also, make sure you check the return value of FindNextFile. It will return false when there are no more matching files and then calling GetLastError will return ERROR_NO_MORE_FILES.

Since you're asking the user for a directory, you need to append a backslash if there isn't one, and an asterisk as a wildcard to match all files and folders within the directory specified.

North~

Member #12,192

August 2010

That fixed it, thank you.

--------------------------------------------------
http://blog.wolfire.com/2009/04/always-initialize-your-memory/

If this is possible if you don't correctly initialize memory, it should be a priority of the highest order.