on_notify_set_file_attributes Event

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

Syntax

class CBMonitorNotifySetFileAttributesEventParams(object):
  @property
  def file_name() -> str: ...
  @property
  def creation_time() -> datetime.datetime: ...
  @property
  def last_access_time() -> datetime.datetime: ...
  @property
  def last_write_time() -> datetime.datetime: ...
  @property
  def change_time() -> datetime.datetime: ...
  @property
  def attributes() -> int: ...
  @property
  def status() -> int: ...
  @property
  def result_code() -> int: ...
  @result_code.setter
  def result_code(value) -> None: ...

# In class CBMonitor:
@property
def on_notify_set_file_attributes() -> Callable[[CBMonitorNotifySetFileAttributesEventParams], None]: ...
@on_notify_set_file_attributes.setter
def on_notify_set_file_attributes(event_hook: Callable[[CBMonitorNotifySetFileAttributesEventParams], None]) -> None: ...

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 in UTC. A value of January 1, 1970 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 nt_status_to_win_32_error method. Please note that this event won't fire for failed requests unless the process_failed_requests 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.