Fires when a directory entry has been returned during directory enumeration.
type TNotifyEnumerateDirectoryEvent = procedure ( Sender: TObject; const DirectoryName: String; const FileName: String; CreationTime: TDateTime; LastAccessTime: TDateTime; LastWriteTime: TDateTime; ChangeTime: TDateTime; Size: Int64; AllocationSize: Int64; FileId: Int64; Attributes: Integer; Status: Integer; var ResultCode: Integer ) of Object;
property OnNotifyEnumerateDirectory: TNotifyEnumerateDirectoryEvent read FOnNotifyEnumerateDirectory write FOnNotifyEnumerateDirectory;
This event fires when a directory entry (i.e., file or subdirectory) has been returned during enumeration of the directory specified by DirectoryName.
The FileName parameter reflects the name of the directory entry.
The CreationTime, LastAccessTime, LastWriteTime, and ChangeTime parameters reflect the entry's time values, specified in UTC.
The Size parameter reflects the size of the file, in bytes; it is always 0 for subdirectories.
The AllocationSize parameter reflects the amount of space allocated for the file, in bytes; it is always 0 for subdirectories.
The FileId parameter reflects the unique Id of the entry, as reported by the filesystem. This Id is used by the network redirector, and some third-party applications, to open files and directories by Id instead of by name. The root directory always uses the predefined Id 0x7FFFFFFFFFFFFFFF.
The Attributes parameter reflects the entry's attributes; please refer to Microsoft's File Attribute Constants article for attribute descriptions.
The Status parameter contains an NT status code that indicates the outcome of the operation; 0 indicates success. To convert this value to a Win32 error code, call the NtStatusToWin32Error method. Please note that this event won't fire for failed requests unless the ProcessFailedRequests property is enabled.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason, set it to a non-zero value to report an appropriate error. Note, however, that this event fires after the operation has already completed, so reporting an error won't actually affect the operation itself. Please refer to the Error Reporting and Handling topic for more information.
This event is fired asynchronously; please refer to the Event Types topic for more information.