NotifySetFileAttributes Event

Fires when a file or directory's attributes and/or times have been changed.

Syntax

virtual int FireNotifySetFileAttributes(CBMonitorNotifySetFileAttributesEventParams *e);
typedef struct {
const char *FileName;
int64 CreationTime;
int64 LastAccessTime;
int64 LastWriteTime;
int64 ChangeTime;
int Attributes;
int Status;
int ResultCode; int reserved; } CBMonitorNotifySetFileAttributesEventParams;
virtual INT FireNotifySetFileAttributes(CBMonitorNotifySetFileAttributesEventParams *e);
typedef struct {
LPCWSTR FileName;
LONG64 CreationTime;
LONG64 LastAccessTime;
LONG64 LastWriteTime;
LONG64 ChangeTime;
INT Attributes;
INT Status;
INT ResultCode; INT reserved; } CBMonitorNotifySetFileAttributesEventParams;

Remarks

This event fires when the attributes and/or times of the file or directory specified by FileName have been changed.

Applications only need to handle this event if they've added a standard filter rule that includes the FS_NE_SET_ATTRIBUTES flag.

The CreationTime, LastAccessTime, LastWriteTime, and ChangeTime parameters reflect the new time values, specified as a number of 100-nanosecond intervals since Jan 1, 1601 00:00:00 UTC. A value of 0 indicates that the corresponding time value was not included in the request.

The Attributes parameter reflects the new 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.

 
 
Copyright (c) 2020 Callback Technologies, Inc. - All rights reserved.
CBFS Filter 2020 C++ Edition - Version 20.0 [Build 7543]