Monitor multiple files failures under Windows about efsw HOT 6 CLOSED

That's a totally reasonable request. I've got to think of a good API for that and make it as a non-breaking change. If you have some minutes can you open a ticket for this specific feature request? Thanks

from efsw.

When you first call ReadDirectoryChangesW, the system allocates a buffer to store change information. This buffer is associated with the directory handle until it is closed and its size does not change during its lifetime. Directory changes that occur between calls to this function are added to the buffer and then returned with the next call. If the buffer overflows, ReadDirectoryChangesW will still return true, but the entire contents of the buffer are discarded and the lpBytesReturned parameter will be zero, which indicates that your buffer was too small to hold all of the changes that occurred.

The buffer is too small for changes that need to monitor a large number of files.

from efsw.

The buffer size was limited because of an old Windows bug, at least that's what it says in the code:

from efsw.

The buffer size was limited because of an old Windows bug, at least that's what it says in the code:
I can probably increase the buffer size.

Yes, what occupies this buffer is actually the string of the file path,so in the case of a large number of files or many long path files, 64k is too small.

from efsw.

In the current implementation, it seems impossible to determine whether the ReadDirectoryChangesW() call has failed or not. Is it possible to provide users with information about any failures, so they can react accordingly?
Another suggestion could be to allow users to specify the buffer size or provide the buffer themselves, enabling them to tailor it to their needs. In this way, the onus is on the users to customize the buffer as necessary.

from efsw.

This issues has been fixes thanks to the @r00tcxx contribution in this PR. :)

from efsw.