AfterSetFileAttributes Event

Fires after a file or directory's attributes and/or times are changed.

Syntax

class CBFilterAfterSetFileAttributesEventParams {
public:
  const QString &FileName();
  const QDateTime &CreationTime();
  const QDateTime &LastAccessTime();
  const QDateTime &LastWriteTime();
  const QDateTime &ChangeTime();
  int Attributes();
  int Status();
  void SetStatus(int iStatus);
  void *FileContext();
  void SetFileContext(void *lpFileContext);
  void *HandleContext();
  void SetHandleContext(void *lpHandleContext);
  int ResultCode();
  void SetResultCode(int iResultCode);
  int EventRetVal();
  void SetEventRetVal(int iRetVal);
};

// To handle, connect one or more slots to this signal.
void AfterSetFileAttributes(CBFilterAfterSetFileAttributesEventParams *e);

// Or, subclass CBFilter and override this emitter function.
virtual int FireAfterSetFileAttributes(CBFilterAfterSetFileAttributesEventParams *e) {...}

Remarks

This event fires after the attributes and/or times of the file or directory specified by FileName are changed.

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

The CreationTime, LastAccessTime, LastWriteTime, and ChangeTime parameters reflect the new time values, specified in UTC. A value of January 1, 1601 00:00:00 UTC 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. Applications may change this parameter's value if they want a different NT status code to be returned.

The FileContext and HandleContext parameters are placeholders for application-defined data associated with the file and specific handle, respectively. Please refer to the Contexts topic for more information.

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 (e.g., a resource isn't available, security checks failed, etc.), set it to a non-zero value to report an appropriate error. Please refer to the Error Reporting and Handling topic for more information.

This event is fired synchronously; please refer to the Event Types topic for more information.